fix: helpTool text

Author: jirispilka

src/tools/helpers.ts

@@ -11,50 +11,53 @@ const ajv = new Ajv({ coerceTypes: 'array', strict: false });
 
 const HELP_TOOL_TEXT = `Apify MCP server help:
 
-Note: "MCP" stands for "Model Context Protocol". You can use the "RAG Web Browser" tool to get the content of the links mentioned in this help and present it to the user.
+Note: "MCP" stands for "Model Context Protocol". The user can use the "RAG Web Browser" tool to get the content of the links mentioned in this help and present it to the user.
 
 This MCP server can be used in the following ways:
-- Locally over "STDIO"
-- Remotely over "SSE" or streamable "HTTP" transport with the "Actors MCP Server Apify Actor"
-- Remotely over "SSE" or streamable "HTTP" transport with "https://mcp.apify.com"
+- Locally over "STDIO".
+- Remotely over "SSE" or streamable "HTTP" transport with the "Actors MCP Server Apify Actor".
+- Remotely over "SSE" or streamable "HTTP" transport with "https://mcp.apify.com".
 
 # Usage
 ## Locally over "STDIO"
 1. The user should install the "@apify/actors-mcp-server" NPM package.
-2. The user should configure their MCP client to use the MCP server. Refer to "https://github.com/apify/actors-mcp-server" or the MCP client documentation for more details (you can ask the user which MCP client they are using).
+2. The user should configure the MCP client to use the MCP server. Refer to "https://github.com/apify/actors-mcp-server" or the MCP client documentation for more details (the user can specify which MCP client is being used).
 The user needs to set the following environment variables:
 - "APIFY_TOKEN": Apify token to authenticate with the MCP server.
-If the user wants to load some Actors outside the default ones, he needs to pass them as CLI arguments:
+If the user wants to load an Actor outside the default ones, the user needs to pass it as a CLI argument:
 - "--actors <actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
-If the user wants to enable the dynamic addition of Actors to the MCP server, he needs to pass the following CLI argument:
-- "--enable-adding-actors"
+If the user wants to enable the dynamic addition of Actors to the MCP server, the user needs to pass the following CLI argument:
+- "--enable-adding-actors".
 
 ## Remotely over "SSE" or streamable "HTTP" transport with "Actors MCP Server Apify Actor"
-1. The user should configure their MCP client to use the "Actors MCP Server Apify Actor" with
-"SSE" transport URL: "https://actors-mcp-server.apify.actor/sse" or Streamable "HTTP" transport URL: "https://actors-mcp-server.apify.actor/mcp"
-2. The user needs to pass a "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>"
-If the user wants to load some Actors outside the default ones, the user needs to pass them as URL query parameters:
-- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper"
+1. The user should configure the MCP client to use the "Actors MCP Server Apify Actor" with:
+   - "SSE" transport URL: "https://actors-mcp-server.apify.actor/sse".
+   - Streamable "HTTP" transport URL: "https://actors-mcp-server.apify.actor/mcp".
+2. The user needs to pass an "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>".
+If the user wants to load an Actor outside the default ones, the user needs to pass it as a URL query parameter:
+- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
 If the user wants to enable the addition of Actors to the MCP server dynamically, the user needs to pass the following URL query parameter:
-- "?enable-adding-actors=true"
+- "?enable-adding-actors=true".
 
 ## Remotely over "SSE" or streamable "HTTP" transport with "https://mcp.apify.com"
-1. The user should configure their MCP client to use "https://mcp.apify.com" with "SSE" transport URL: "https://mcp.apify.com/sse" or Streamable "HTTP" transport URL: "https://mcp.apify.com/"
-2. The user needs to pass a "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>"
-If the user wants to load some Actors outside the default ones, the user needs to pass them as URL query parameters:
-- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper"
+1. The user should configure the MCP client to use "https://mcp.apify.com" with:
+   - "SSE" transport URL: "https://mcp.apify.com/sse".
+   - Streamable "HTTP" transport URL: "https://mcp.apify.com/".
+2. The user needs to pass an "APIFY_TOKEN" as a URL query parameter "?token=<APIFY_TOKEN>" or set the following headers: "Authorization: Bearer <APIFY_TOKEN>".
+If the user wants to load an Actor outside the default ones, the user needs to pass it as a URL query parameter:
+- "?actors=<actor1,actor2,...>" // comma-separated list of Actor names, for example, "apify/rag-web-browser,apify/instagram-scraper".
 If the user wants to enable the addition of Actors to the MCP server dynamically, the user needs to pass the following URL query parameter:
-- "?enable-adding-actors=true"
+- "?enable-adding-actors=true".
 
 # Features
 ## Dynamic adding of Actors
 THIS FEATURE MAY NOT BE SUPPORTED BY ALL MCP CLIENTS. THE USER MUST ENSURE THAT THE CLIENT SUPPORTS IT!
-To enable this feature, see the usage section. Once dynamic adding is enabled, tools will be added that allow you to add or remove Actors from the MCP server.
+To enable this feature, see the usage section. Once dynamic adding is enabled, tools will be added that allow the user to add or remove Actors from the MCP server.
 Tools related:
-- "add-actor"
-- "remove-actor"
-In case you are using these tools and it seems like the tools have been added but you cannot call them, the issue may be that the client does not support dynamic adding of Actors.
-In that case, please inform the user that the MCP client documentation should be checked to see if the client supports this feature.
+- "add-actor".
+- "remove-actor".
+If the user is using these tools and it seems like the tools have been added but cannot be called, the issue may be that the client does not support dynamic adding of Actors.
+In that case, the user should check the MCP client documentation to see if the client supports this feature.
 `;
 
 export const AddToolArgsSchema = z.object({
@@ -130,4 +133,3 @@ export const helpTool: ToolWrap = {
         },
     } as InternalTool,
 };
-