［AI 與科技名詞白話解釋］模糊搜尋本站的 AI 名詞、概念比較與實作教學。
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": {
"q": "<q>"
},
"name": "glossary__search_glossary"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | ||
| limit | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose that search is fuzzy (模糊) and scoped to the site, but says nothing about result format, ranking behavior, pagination, limit behavior, or any other operational detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence, front-loading the content scope before the action. It avoids repetition and waste, though its brevity contributes to gaps elsewhere rather than being a conciseness problem itself.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter search tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It does not explain parameter usage or distinguish this tool from overlapping glossary siblings, which an agent needs in order to select it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description does not mention either parameter. It does not explain what q should contain or how limit affects the search, leaving both parameters entirely undocumented in the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (模糊搜尋 / fuzzy search) and resource (本站的 AI 名詞、概念比較與實作教學 / this site's AI terms, concept comparisons, and implementation tutorials). It is clear what the tool does, but it does not differentiate from sibling glossary tools such as explain_term, compare_concepts, or get_howto.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus its glossary siblings. The description implies it is a search tool, but gives no conditions, exclusions, or alternative-routing advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.