Remove tool filtering and update docs

Author: cameroncooke

README.md

@@ -20,11 +20,11 @@ A Model Context Protocol (MCP) server that provides Xcode-related tools for inte
 - [Getting started](#getting-started)
   - [Prerequisites](#prerequisites)
   - [Configure your MCP client](#configure-your-mcp-client)
-    - [MCP Feature Compatibility](#mcp-feature-compatibility)
     - [Quick install](#quick-install)
     - [Manual installation](#manual-installation)
     - [Alternative installation method using mise](#alternative-installation-method-using-mise)
     - [Installing via Smithery](#installing-via-smithery)
+    - [MCP Compatibility](#mcp-compatibility)
 - [Incremental build support](#incremental-build-support)
 - [Code Signing for Device Deployment](#code-signing-for-device-deployment)
 - [Troubleshooting](#troubleshooting)
@@ -97,11 +97,9 @@ The XcodeBuildMCP server provides the following tool capabilities:
 
 ### MCP Resources
 
-For clients that support MCP resources (VS Code, Claude Code, Claude Desktop), XcodeBuildMCP provides efficient URI-based data access:
+For clients that support MCP resources XcodeBuildMCP provides efficient URI-based data access:
 
-- **Simulators Resource** (`mcp://xcodebuild/simulators`): Direct access to available iOS simulators with UUIDs and states
-- **Automatic Fallback**: Clients without resource support automatically use equivalent tool-based APIs
-- **Smart Filtering**: Redundant tools are filtered out when resources are available to prevent duplicate functionality
+- **Simulators Resource** (`xcodebuildmcp://simulators`): Direct access to available iOS simulators with UUIDs and states
 
 > [!IMPORTANT]
 > Please note that XcodeBuildMCP will request xcodebuild to skip macro validation. This is to avoid errors when building projects that use Swift Macros. 
@@ -116,24 +114,6 @@ For clients that support MCP resources (VS Code, Claude Code, Claude Desktop), X
 
 ### Configure your MCP client
 
-#### MCP Feature Compatibility
-
-XcodeBuildMCP supports both MCP tools and resources. Different editors have varying levels of MCP feature support:
-
-| Editor | Tools | Resources | Notes |
-|--------|-------|-----------|-------|
-| **VS Code** | ✅ | ✅ | Full MCP specification support |
-| **Cursor** | ✅ | ❌ | Tools only - resources not supported |
-| **Windsurf** | ✅ | ❌ | Tools and discovery only |
-| **Claude Code** | ✅ | ✅ | Full support for resources, tools, and routes |
-| **Claude Desktop** | ✅ | ✅ | Full support for resources, tools, and prompts |
-
-**Resources vs Tools:**
-- **Tools**: Function-based API calls (e.g., `list_sims()` to get simulator list)
-- **Resources**: Efficient data access via URIs (e.g., `mcp://xcodebuild/simulators` for simulator data)
-
-XcodeBuildMCP automatically detects your client's capabilities and provides the most appropriate interface. Clients with resource support get efficient URI-based data access, while others fall back to traditional tool calls.
-
 #### Quick install
 
 For a quick install, you can use the following links:
@@ -201,6 +181,18 @@ To install XcodeBuildMCP Server for Claude Desktop automatically via [Smithery](
 npx -y @smithery/cli install @cameroncooke/XcodeBuildMCP --client claude
 ```
 
+#### MCP Compatibility
+
+XcodeBuildMCP supports both MCP tools, resources and sampling. At time of writing the following editors have varying levels of MCP feature support:
+
+| Editor | Tools | Resources | Samplng |
+|--------|-------|-----------|---------|
+| **VS Code** | ✅ | ✅ | ✅ |
+| **Cursor** | ✅ | ❌ | ❌ | 
+| **Windsurf** | ✅ | ❌ | ❌ |
+| **Claude Code** | ✅ | ✅ | ❌ |
+| **Claude Desktop** | ✅ | ✅ | ❌ |
+
 ## Incremental build support
 
 XcodeBuildMCP includes experimental support for incremental builds. This feature is disabled by default and can be enabled by setting the `INCREMENTAL_BUILDS_ENABLED` environment variable to `true`:

docs/ARCHITECTURE.md

@@ -30,27 +30,26 @@ XcodeBuildMCP is a Model Context Protocol (MCP) server that exposes Xcode operat
 
 ```
 ┌────────────────────────────────────────────────────────────┐
-│            Presentation / Transport Layer                   │
+│            Presentation / Transport Layer                  │
 │  • src/server/server.ts  – MCP server creation & transport │
 │  • src/index.ts          – process entry, Sentry boot,     │
-│                            plugin loading, lifecycle        │
+│                            plugin loading, lifecycle       │
 └────────────────────────────────────────────────────────────┘
 ┌────────────────────────────────────────────────────────────┐
 │            Plugin Discovery & Registration Layer           │
 │  • src/core/plugin-registry.ts  – automatic plugin loading │
-│  • src/core/plugin-types.ts     – plugin type definitions  │
-│  • plugins/**/                  – self-contained plugins    │
+│  • src/core/plugin-types.ts     – plugin type definitions   │
+│  • plugins/**/                  – self-contained plugins   │
 └────────────────────────────────────────────────────────────┘
 ┌────────────────────────────────────────────────────────────┐
 │                    MCP Resources Layer                     │
 │  • src/core/resources.ts        – resource management      │
 │  • src/resources/**/            – MCP resource handlers    │
-│  • Client capability detection  – automatic tool filtering │
 └────────────────────────────────────────────────────────────┘
 ┌────────────────────────────────────────────────────────────┐
 │                   Plugin Implementation Layer              │
-│  • plugins/**/**.js – one file per tool capability         │
-│  • Common patterns:                                         │
+│  • plugins/**/**.js – one file per tool capability          │
+│  • Common patterns:                                        │
 │      – Standardized plugin exports (name, schema, handler) │
 │      – Zod schemas for param validation                    │
 │      – Uniform ToolResponse payloads                       │
@@ -259,29 +258,56 @@ export function supportsResources(server?: unknown): boolean {
 }
 ```
 
-#### Smart Tool Filtering
-
-When resources are available, redundant tools are automatically filtered:
-
-- **Resource-supported clients**: Get `mcp://xcodebuild/simulators` resource
-- **Tool-only clients**: Keep `list_sims` tool for compatibility
-- **Automatic detection**: No client configuration required
-
 #### Resource Implementation Pattern
 
-Resources reuse existing tool logic for consistency:
+Resources can reuse existing tool logic for consistency:
 
 ```typescript
-// src/resources/simulators.ts
+// src/resources/some_resource.ts
 export default {
-  uri: 'mcp://xcodebuild/simulators',
-  description: 'Available iOS simulators with UUIDs and states',
+  uri: 'xcodebuildmcp://some_resource',
+  name: 'some_resource',
+  description: 'Returns some resource information',
   mimeType: 'text/plain',
-  async handler(executor = getDefaultCommandExecutor()) {
-    // Reuses list_simsLogic for consistency
-    const result = await list_simsLogic({}, executor);
-    return { contents: [{ type: 'text', text: result.content[0].text }] };
-  }
+  async handler(
+    uri: URL,
+    executor: CommandExecutor = getDefaultCommandExecutor(),
+  ): Promise<{ contents: Array<{ text: string }> }> {
+    try {
+      log('info', 'Processing simulators resource request');
+
+      const result = await getSomeResource({}, executor);
+
+      if (result.isError) {
+        const errorText = result.content[0]?.text;
+        throw new Error(
+          typeof errorText === 'string' ? errorText : 'Failed to retrieve some resource data',
+        );
+      }
+
+      return {
+        contents: [
+          {
+            text:
+              typeof result.content[0]?.text === 'string'
+                ? result.content[0].text
+                : 'No data for that resource is available',
+          },
+        ],
+      };
+    } catch (error) {
+      const errorMessage = error instanceof Error ? error.message : String(error);
+      log('error', `Error in some_resource resource handler: ${errorMessage}`);
+
+      return {
+        contents: [
+          {
+            text: `Error retrieving resource data: ${errorMessage}`,
+          },
+        ],
+      };
+    }
+  },
 };
 ```