Skip to main content
Glama

update_mcp_server_capabilities

Destructive

Enable or disable MCP server capabilities, with changes taking effect immediately and overriding integration-level settings; inspect current capabilities first to review the surface.

Instructions

Enable or disable capabilities on an MCP server. Changes take effect immediately and override the integration-level settings for this server; use list_mcp_server_capabilities first to inspect the current surface.

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>",
      "capabilities": "<capabilities>"
    },
    "name": "update_mcp_server_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe MCP server ID or slug
capabilitiesYesArray of capability updates

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, which tells the agent that this operation is consequential and materially changes remote state. The description adds genuinely useful context beyond that: changes take effect immediately and override the integration-level settings for this server. It does not, however, explain what an existing capability's configuration loses when it is disabled or whether omitted capabilities survive the call. The annotation coverage means this limited context still suffices, so a 3 is appropriate.

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 sentences, both earning their place. The effect and precedence statement comes first, and the prerequisite pointer follows. There is no restating of the tool name, no filler, and no redundant explanation of the parameters already documented in the schema.

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?

This hits nearly everything an agent needs: the effective-immediately semantics, the precedence relationship to integration-level settings, the prerequisite inspection step, and the full parameter schema plus an output schema. The one omission that matters is whether the capabilities array is additive or replacing, which is important given destructiveHint=true. A short clause on that would make this complete.

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%: 'id' (server ID or slug) and the 'capabilities' array all carry per-field descriptions, so the schema does the heavy lifting and a baseline of 3 is correct. The description adds no meaning beyond the schema about how the array is applied. Specifically, it does not clarify whether 'capabilities' is a full replacement set or a partial patch. That matters for a destructive, non-idempotent call.

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?

The description gives a specific verb pair ('enable or disable') and a specific resource ('capabilities on an MCP server'), and it implicitly distinguishes itself from the sibling update_mcp_integration_capabilities by noting that changes 'override the integration-level settings for this server.' It stops short of naming that sibling outright, so an agent must infer the pairing from the wording rather than being routed explicitly.

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?

It states a clear prerequisite workflow: 'use list_mcp_server_capabilities first to inspect the current surface,' which is a concrete ordering constraint tied to a real sibling tool. What it lacks is any when-not guidance, for example whether bulk capability changes should instead go through update_mcp_integration_capabilities or how to handle capabilities that don't yet exist.

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

Deploy Server

Other Tools