fix: Rename tool name, sent notifications/tools/list_changed

.actor/input_schema.json

@@ -17,7 +17,7 @@
         "enableActorAutoLoading": {
             "title": "Enable automatic loading of Actors based on context and use-case (experimental, check if it supported by your client)",
             "type": "boolean",
-            "description": "When enabled, the server can dynamically add Actors as tools based on user requests and context. \n\nNote: Not all MCP clients support this feature. To try it, you can use the [Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client). This is an experimental feature and may require client-specific support.",
+            "description": "When enabled, the server can dynamically add Actors as tools based on user requests and context. \n\nNote: MCP client must support notification on tool updates. To try it, you can use the [Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client). This is an experimental feature and may require client-specific support.",
             "default": false
         },
         "maxActorMemoryBytes": {

.github/workflows/check.yaml

@@ -13,8 +13,8 @@ on:
             - "**" # Ignore all tags to prevent duplicate builds when tags are pushed.
 
 jobs:
-    lint:
-        name: Lint
+    lint_and_test:
+        name: Build & Test
         runs-on: ubuntu-latest
 
         steps:
@@ -27,4 +27,12 @@ jobs:
                     cache-dependency-path: 'package-lock.json'
             -   name: Install Dependencies
                 run: npm ci
-            -   run: npm run lint
+
+            -   name: Lint
+                run: npm run lint
+
+            -   name: Build
+                run: npm run build
+
+            -   name: Test
+                run: npm run test

README.md

@@ -96,7 +96,7 @@ The server provides a set of helper tools to discover available Actors and retri
 - `get-actor-details`: Retrieves documentation, input schema, and details about a specific Actor.
 - `discover-actors`: Searches for relevant Actors using keywords and returns their details.
 
-There are also tools to manage the available tools list. However, dynamically adding and removing tools requires the MCP client to have the capability to manage the tools list, which is typically not supported.
+There are also tools to manage the available tools list. However, dynamically adding and removing tools requires the MCP client to have the capability to update tools list (handle `ToolListChangedNotificationSchema`), which is typically not supported.
 
 You can try this functionality using the [Apify Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client) Actor.
 To enable it, set the `enableActorAutoLoading` parameter.
@@ -393,3 +393,4 @@ If you need other features or have any feedback, [submit an issue](https://conso
 - [What is MCP and why does it matter?](https://blog.apify.com/what-is-model-context-protocol/)
 - [Tester MCP Client](https://apify.com/jiri.spilka/tester-mcp-client)
 - [AI agent workflow: building an agent to query Apify datasets](https://blog.apify.com/ai-agent-workflow/)
+- [MCP Client development guide](https://github.com/cyanheads/model-context-protocol-resources/blob/main/guides/mcp-client-development-guide.md)