Skip to main content
Glama

Set MCP server enabled

set_mcp_server_enabled
Destructive

Enable or disable a registered MCP tool server. Organisation admins only. Disabling immediately withdraws the server's tools from every agent run; enabling restores them (existing grants and the allow-list still apply).

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": "<server>",
      "enabled": "<enabled>"
    },
    "name": "set_mcp_server_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesThe registered server's name or id (see list_mcp_servers).
enabledYestrue to enable, false to disable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and readOnlyHint=false, but the description earns its place by describing the actual blast radius: tools are withdrawn from every agent run immediately, and re-enabling does not restore grants or bypass the allow-list. The only minor tension is that a state-setting toggle reads as naturally idempotent, which pushes against idempotentHint=false.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the action, then the permission gate, then the consequences. Every sentence carries information; no redundancy or filler.

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 two-parameter toggle with annotations covering the safety profile and no output schema, this covers permission requirements, immediate effect, and the non-restoration caveat. A note on what happens for an unknown or unregistered server name would close the remaining gap.

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 100% and both parameters are documented in the schema, including the pointer to list_mcp_servers for the server identifier. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 pair and a precise resource: 'Enable or disable a registered MCP tool server.' The object is narrowly scoped to MCP servers, which cleanly separates it from register_mcp_server and list_mcp_servers without needing to name them.

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?

'Organisation admins only' gives an explicit callable prerequisite, and the described effect implies the operational context (toggling an already-registered server). It stops short of naming when to choose this over an alternative or spelling out exclusions, so it sits just below the top band.

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.