Skip to main content
Glama

Turn on a hosted MCP server

enable
Idempotent

Starts a hosted MCP server, registers its tools under server__tool names, and returns tool count, samples, and instructions. Use it to add a server's tools to the current session.

Instructions

Starts a hosted MCP server and adds its tools, named __. Servers with policy confirm ask a person first; deny servers cannot be enabled. Returns the tool count, sample tool names and the server's instructions.

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

Input Schema

NameRequiredDescriptionDefault
nameYesServer name, as listed by servers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the tool-name namespacing convention ('<server>__<tool>'), the policy-based gating (a confirm prompt to a human, hard denial for deny-policy servers), and the exact shape of the response (tool count, sample names, server instructions). The annotations already flag it as non-read-only and idempotent, and nothing here conflicts with them.

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, each doing distinct work: what happens, what blocks it, what comes back. The primary action is front-loaded and there is no filler.

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

Completeness5/5

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

No output schema exists, so the description's account of the return values is necessary and it supplies it. For a one-parameter state-changing tool with strong annotations, an agent has everything needed: eligibility, side effects, and result shape.

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% with a single well-described 'name' property ('Server name, as listed by servers'), so the schema carries the parameter burden. The description adds no format or edge-case detail about the name beyond that, so the baseline 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 ('Starts') and resource ('hosted MCP server'), then names the concrete side effect of adding tools prefixed '<server>__<tool>'. This is distinguishable at a glance from siblings like disable, restart, and servers, without opening any schema.

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 real eligibility conditions: servers with policy 'confirm' prompt a person first, and servers with policy 'deny' cannot be enabled at all. It doesn't explicitly route the agent to `disable` or `servers` for the inverse workflows, but the preconditions for calling this tool are clearly stated.

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