OnlyMCP

Update a connection

connection_update

Idempotent

Change a connected MCP server. Only the fields you pass are touched. Changing url, transport, authType or the secret triggers a fresh probe. Docs: https://only-mcp.com/docs/mcp-servers#how-a-server-signs-in

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": {
      "slug": "<slug>"
    },
    "name": "connection_update"
  }
}

Input Schema

Name	Required	Description
`url`	No	New https URL. A new address drops the stored secret and every authorization of this connection: pass secret in the same call to keep a bearer or header connection working.
`name`	No	New human readable name.
`slug`	Yes	Which connection, by its slug.
`secret`	No	Replace the credential.
`enabled`	No	false takes its tools out of the gateway.
`authType`	No	none, bearer or header. Switching to none clears the stored secret.
`transport`	No	http or sse.
`authHeaderName`	No	Only for authType header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true; the description adds real value beyond them by disclosing the re-probe side effect on credential/transport/url changes and the patch-only mutation model. It stops short of describing propagation timing or what a probe failure does to the connection.

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?

Three short sentences, zero filler, with the core mutation model front-loaded before the side-effect warning and the doc link. Nothing repeats the title.

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 an eight-parameter mutation tool with no output schema, the description plus rich schema covers the essentials: identity parameter, patch semantics, and probe triggers. It could say more about what the caller gets back or whether a probe failure rolls back the change, but nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so every one of the eight parameters is already documented in the schema, including the non-obvious consequence that a new url drops the stored secret. The description adds no parameter-level meaning of its own, which lands at the baseline for fully covered schemas.

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: 'Change a connected MCP server', and the second sentence pins down the partial-update semantics ('Only the fields you pass are touched'). It does not explicitly name connection_create/connection_delete as the alternatives, so distinguishing it from siblings is left partly to inference.

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

Usage Guidelines3/5

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

The description gives operating conditions — partial updates, and that url/transport/authType/secret changes trigger a fresh probe — plus a docs pointer. It never states when to use this versus connection_create or connection_delete, so the when-to-use guidance is implied rather than explicit.

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

All OnlyMCP tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?