AiLinkAny

Refresh MCP server tool catalog

mcp_manager_refresh_server

Refreshes tools/list for one enabled downstream MCP server through the target computer's local Runtime and updates catalog_version only when the downstream tool catalog changes. Use after a successful add/update/test when fresh capabilities are needed. Select this tool from the user's intent when it is the best match. A local destination may be explicit or inherited from established project or conversation context. The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server_id": "<server_id>"
    },
    "name": "mcp_manager_refresh_server"
  }
}

Input Schema

Name	Required	Description
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`server_id`	Yes
`device_name`	No	Computer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
`retry_token`	No	New opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
`workflow_id`	No	Optional workflow id; pass together with ai_session_id.
`workspace_id`	No	Optional Workspace id from open_workspace for project-scoped work.
`ai_session_id`	No	Optional Session id. Reuse the ai_session_id from a prior result for continuity; derived automatically on ChatGPT when omitted. Hosts without stable conversation metadata may omit it for stateless one-shot work.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-idempotent, non-destructive, and open-world behavior. The description adds meaningful context beyond that: the refresh runs through the target computer's local Runtime, only enabled servers are eligible, and catalog_version changes only when the downstream catalog actually differs. It does not discuss auth requirements, rate limits, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tightly front-loaded and specific about operation and trigger. The remaining sentences ('Select this tool from the user's intent when it is the best match,' 'The user does not need to mention ailinkany.com...') are generic routing boilerplate that dilutes the tool-specific content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description supplies the operational context an agent needs: the trigger, the conditional side effect, and the local-Runtime routing. A note on behavior when the server is not enabled or the refresh fails would make it fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the schema already documents device_id, device_name, retry_token, and the session/workspace parameters. The description only generally references 'one enabled downstream MCP server' and an inheritable 'local destination,' adding little format or selection guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Refreshes tools/list for one enabled downstream MCP server') plus the precise side effect (catalog_version updated only when the catalog changes). An agent can distinguish this from the add/update/test/enable siblings by the refresh semantics and the 'after a successful add/update/test' trigger.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger ('Use after a successful add/update/test when fresh capabilities are needed') and clarifies that the destination may be inherited from project or conversation context. It stops short of naming exclusions or alternatives—e.g., when to prefer mcp_gateway_list_tools or mcp_gateway_session_sync—so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AiLinkAny tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?