Retrieve the translation glossary to check terminology and supported terms. Filter by locale code to view entries for a specific language.
Export the built-in glossary/terminology dictionary. Use this when user wants to view or check the translation glossary. Optionally filter by locale.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Optional locale code to filter (e.g., 'zh-CN'). If omitted, returns all locales. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a read-only export operation, which is useful behavioral context given no annotations. However, it does not disclose the return format, pagination, or any limits, which would add more transparency.
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?
Two sentences with no wasted words. The key action and usage context are front-loaded, and the optional filtering behavior is stated concisely.
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 simple one-optional-parameter tool, the description covers purpose, usage context, and filtering. The main gap is the lack of return format detail, but the output is implied to be the glossary/terminology dictionary.
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?
The schema already describes the locale parameter fully, and description adds only a brief 'Optionally filter by locale' without adding new semantic detail. Baseline 3 is appropriate given the 100% schema coverage.
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 uses a specific verb and resource: 'Export the built-in glossary/terminology dictionary.' It clearly tells an agent what the tool does and differentiates it from the sibling tools translate_page and check-i18n by focusing on viewing/checking the glossary rather than translating or checking i18n.
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?
Explicitly states when to use: 'Use this when user wants to view or check the translation glossary.' It provides clear context though it does not explicitly mention alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.