Skip to main content
Glama

mcp_call

Routes a tool call to a project-bound or file-bound child MCP instance, letting an agent use one global MCP configuration while isolating calls by project.

Instructions

代理执行子 MCP 的工具。project 决定绑定到哪个项目(sqlite 会指向该项目的库文件)。

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": {
      "mcp": "<mcp>",
      "tool": "<tool>"
    },
    "name": "mcp_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
mcpYes
argsNo
toolYes
projectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one non-obvious behavioral trait: project determines the binding target, and for sqlite it selects that project's database file. However, for an arbitrary code-execution proxy it says nothing about side effects, whether the inner tool can be destructive, prerequisite lifecycle, or error propagation.

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 short sentences with no filler, and the core purpose is front-loaded before the project clarifier. It is efficient rather than bloated, though the parenthetical second sentence is compressed to the point of being cryptic.

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

Completeness3/5

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

The presence of an output schema relieves the description of explaining return values, which helps. But with four parameters at 0% schema coverage and no annotations on a generic execution proxy, the definition leaves the agent without enough information to invoke it confidently.

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%, so the description must compensate, but it only addresses one of four parameters (project). It says nothing about what mcp identifies (name vs. id), that tool should be a tool name obtained from mcp_tools, or that args must conform to the target tool's own schema.

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 states a specific verb and resource: it proxies execution of a tool that belongs to a sub-MCP server. That is meaningfully distinct from siblings like mcp_tools or mcp_list, though the description never names a sibling or explicitly contrasts itself with one.

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 explicit when-to-use guidance, no prerequisite chain (does the target MCP need to be installed/started first?), and no mention of when to prefer mcp_tools or mcp_get instead. The intended usage is only implied by the word 'executes'.

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