Skip to main content
Glama

mcp_tools

Discovers tools exposed by a named child MCP and starts that project instance on demand, enabling dynamic routing under a single MCP configuration.

Instructions

发现某个子 MCP 暴露的工具。会按需启动该项目的实例。

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": "mcp_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
projectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does creditably disclose a non-obvious lifecycle side effect: the project's instance may be launched on demand. It omits whether the instance stays running, whether the call blocks on startup, timing risk, or failure modes, which matter for a tool that mutates runtime state.

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?

Two tight sentences with the core purpose front-loaded and zero padding. The brevity is appropriate, though it edges toward under-specification given the unannotated side effects.

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?

An output schema is present, so return values need not be described. However, for a 2-parameter tool with zero schema coverage and no annotations, the definition leaves the identifier semantics and the lifecycle consequences of the on-demand startup unexplained, which is not enough to call it safely.

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% for 2 parameters, including a required 'name' and an optional 'project', so the description must compensate. It only hints that 'name' identifies a child MCP and 'project' scopes an instance; it never defines the accepted format of either, or what happens when 'project' is omitted.

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 uses a specific verb and resource: 'discover the tools exposed by a child MCP.' An agent can identify the capability without opening the schema. It does not explicitly distinguish itself from siblings such as mcp_list or mcp_get, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool versus mcp_list, mcp_get, or mcp_call, and no prerequisites or exclusions. The edge-triggered side effect ('starts the instance on demand') is mentioned, but the description never says what should lead an agent to choose this tool over a plain listing.

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