Skip to main content
Glama

mcp_get

Fetch the full configuration and instance key for a named child MCP to inspect project- or file-bound settings and routing details.

Instructions

查看某个子 MCP 的完整配置与实例 Key。

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden of explaining behavior. It does add useful return context, stating that the full configuration and an instance Key are returned (the Key being sensitive data), and 查看 implies a read-only operation. It says nothing about permissions, error behavior when the name is unknown, or whether the Key is redacted.

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?

The description is a single short sentence that leads with the action and the scope, with no filler or redundancy.

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?

An output schema exists, so return values need not be explained in detail, and the one-parameter surface is small. Still, for a config/secret-retrieval tool with no annotations, the description leaves the parameter format and the handling of the instance Key underexplained.

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 0%: the single 'name' parameter has no description at all. The description compensates partly by making clear that the name identifies a specific sub-MCP, but it does not state the expected format (identifier vs display name), matching rules, or whether it must match a value from mcp_list.

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 clear verb (查看) and a clear resource (某个子 MCP 的完整配置与实例 Key), so the tool is obviously a single-item config read. It distinguishes itself implicitly from the sibling mcp_list because it targets one named sub-MCP rather than enumerating them, but it never explicitly contrasts the two.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 某个子 MCP suggests the agent must already know which MCP it wants, which indirectly separates this tool from the enumeration done by mcp_list. There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named.

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