AiLinkAny

Update MCP server in local Gateway

mcp_manager_update_server

Updates one existing downstream MCP server through the same local Manager Service used by the desktop UI. Read mcp_gateway_list_servers first and pass its current config_revision. server_id is immutable. environment/headers contain only secret_ref bindings; this tool never receives or returns secret plaintext. On CONFIG_REVISION_CONFLICT, re-read the Registry before retrying so an AI cannot overwrite a concurrent UI change. 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": {
      "expected_revision": "<expected_revision>",
      "server_id": "<server_id>",
      "name": "<name>",
      "transport_type": "<transport_type>"
    },
    "name": "mcp_manager_update_server"
  }
}

Input Schema

Name	Required	Description
`url`	No
`args`	No
`name`	Yes
`command`	No
`enabled`	No
`headers`	No	Optional full HTTP Header-Name -> secret_ref binding map. Omit to preserve existing bindings.
`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.
`environment`	No	Optional full stdio ENV_NAME -> secret_ref binding map. Omit to preserve existing bindings.
`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.
`transport_type`	Yes
`expected_revision`	Yes
`working_directory`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the safety profile is known. The description adds real value beyond that: server_id is immutable, environment/headers carry only secret_ref bindings and the tool never receives or returns secret plaintext, and concurrent UI edits must be re-read after a revision conflict. It does not state how non-mentioned fields behave on a full update (reset vs. preserve) outside of the headers/environment omission rule.

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 operational content (prerequisite read, immutable id, secret refs, conflict retry) is front-loaded and useful. The trailing sentences about intent matching, inherited destinations, and the user not needing to mention ailinkany.com/MCP/connector names are meta-prompt filler that does not document the tool and lengthens the definition without informing invocation.

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?

For a 17-parameter mutation tool with an output schema, the description covers the critical hazards: optimistic concurrency via expected_revision, immutable identity, secret handling, and conflict recovery. Remaining gaps are secondary (partial-update semantics, overlap with mcp_manager_set_server_enabled), and return-value shape is covered by the output schema.

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

Parameters4/5

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

With 47% schema coverage over 17 parameters, the description compensates meaningfully by tying expected_revision to mcp_gateway_list_servers output, flagging server_id as immutable, and explaining that environment/headers are secret_ref binding maps with no plaintext. It still says nothing about the transport_type/url/command/working_directory relationship, which is the main semantic gap left by the schema.

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

Purpose4/5

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

States a specific verb and resource ('Updates one existing downstream MCP server') and scopes it to the local Manager Service used by the desktop UI. It does implicitly separate 'existing' updates from mcp_manager_add_server, but never names the sibling add/remove/enable tools, so the distinction requires inference.

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 concrete prerequisite ('Read mcp_gateway_list_servers first and pass its current config_revision') plus a recovery path on CONFIG_REVISION_CONFLICT. It lacks explicit when-not/alternative guidance (e.g. use mcp_manager_set_server_enabled to just toggle 'enabled'), and the sentence 'Select this tool from the user's intent when it is the best match' is generic rather than directive.

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?