Skip to main content
Glama

update_mcp_server

Update an MCP server configuration and reconnect. Use when changing URL, transport, headers, or name of an outbound connector.

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": {
      "id": "<id>"
    },
    "name": "update_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
urlNo
nameNo
headersNo
transportNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's main contribution is the 'and reconnect' side effect, which tells the agent that the live connection is re-established after the change — real operational context not present in annotations. It does not disclose whether unlisted fields are preserved or whether headers replace or merge, leaving some mutation semantics unstated.

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

Conciseness5/5

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

Two short sentences with zero filler: the mutation and its reconnect effect are front-loaded, and the second sentence is pure usage guidance. Nothing here could be cut without losing information.

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

Completeness2/5

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

For a 5-parameter mutation tool with 0% schema coverage and no output schema, the definition is thin: partial-update behavior, accepted transport values, and the result of the update/reconnect are all unspecified. The safety annotations help, but an agent still cannot confidently fill in parameters or predict the effect of the call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, yet it mostly echoes property names already visible in the schema (url, name, headers, transport). It never explains the required id, whether omitted fields are left unchanged, how headers are merged, or what valid transport values are — and the schema has no enums for transport, so that gap is meaningful.

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 (update an MCP server configuration) plus the fields in scope, and the word 'reconnect' signals the effect. It is distinguishable from create/delete/get MCP server siblings by the update verb, but it does not explicitly contrast itself with connect_mcp_server, which could plausibly also re-establish a connection.

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?

'Use when changing URL, transport, headers, or name of an outbound connector' gives a clear trigger condition tied to concrete fields and clarifies the object is an outbound connector. There are no exclusions (e.g., don't use this to bootstrap a new server) and no named alternative, so it stops short of the 5 bar.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources