Skip to main content
Glama

China Source · 中国信源

Find China Source entries

find
Read-only

中国信源检索:按关键词找结构化官方条目(zh/en, JSON-LD)。命中后可用 get 取全文。只读。

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

Input Schema

NameRequiredDescriptionDefault
limitNo条数, 默认 5
queryYes关键词/问题

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"条数, 默认 20"New value: +"条数, 默认 5"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotation already declares readOnlyHint=true, and the description's trailing '只读' merely restates it. The genuinely additive behavioral content is the result shape (structured official entries, zh/en, JSON-LD) and the two-step search-then-fetch workflow, which is useful but not rich.

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 clauses, zero filler, with the core purpose front-loaded before the follow-up action and the read-only note. Every phrase carries information.

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

Completeness4/5

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

For a two-parameter read-only search with no output schema, the description covers purpose, input modality (keyword), result format (structured zh/en JSON-LD entries), and the next step (get). Only minor gaps remain, such as the limit default and whether results are paginated.

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% — 'query' is documented as 关键词/问题 and 'limit' as 条数, 默认 5 — so the schema already carries parameter meaning. The description's '按关键词' only reinforces the query parameter and adds nothing about limit or result sizing.

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 and resource ('中国信源检索:按关键词找结构化官方条目'), and names the follow-up sibling 'get' for full text, so the agent can tell it apart from a full-text fetch. It does not, however, contrast itself with the other sibling 'list', which is the closest alternative for enumeration.

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 clear context: use it for keyword-based lookup, then switch to 'get' once you have a hit. This is an explicit hand-off instruction. It lacks any when-not condition (e.g. when to prefer 'list'), so it stops short of the top score.

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