Skip to main content
Glama

China Source · 中国信源

Get a China Source entry

get
Read-only

中国信源取件:按 id(@id/identifier) 或相对路径取条目全文。只读。

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

Input Schema

NameRequiredDescriptionDefault
idYes条目 id 或相对路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true is already declared in annotations, and "只读" merely restates it. The genuine added context is that the tool returns the full entry text (全文), which is useful for a read tool. No detail on output size, missing-item behavior, or path resolution limits beyond the annotation baseline.

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?

One compact sentence with the action and accepted input forms front-loaded, followed by the read-only tag. No padding, though the extreme brevity leaves little room for routing or constraint information.

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?

For a one-parameter read-only tool with annotations carrying the safety profile and no output schema, the definition is adequate: it names the resource, accepted inputs, and that full text is returned. It does not address lookups by path versus id differences or failure modes, leaving modest gaps.

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 description coverage is 100%, so the single id parameter is already documented as "条目 id 或相对路径". The description largely mirrors this, though the "@id/identifier" prefix form adds a small format hint. Correct baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb+resource: fetch the full text (全文) of an entry from the China Source by id or relative path. An agent can tell this is a retrieval tool, but the description never contrasts it with the sibling tools find and list, so sibling differentiation is absent.

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?

The description implies usage by specifying how to identify the item (id or relative path), but gives no explicit when-to-use or when-not-to-use guidance and never mentions the alternatives find or list. An agent is left to infer that this is for fetching a known entry versus searching.

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.

Resources