get_paperFetch one AIO paper by id (e.g. "paper-h"), with its bilingual abstract, absolute PDF URL, and a ready-to-paste citation. CC BY 4.0.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Paper id as returned by list_papers, e.g. "paper-h". |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly, idempotent, and non-destructive. The description adds return-value details (abstract, PDF URL, citation) and license (CC BY 4.0), providing useful context beyond annotations.
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 concise sentence, front-loaded with the verb 'Fetch', includes an example and key outputs, with no unnecessary words.
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?
With only one parameter and no output schema, the description covers purpose, id format, return contents, and license, making it fully sufficient for an agent to invoke the tool 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?
The schema fully documents the only parameter 'id' with description and example. The description repeats the same example, adding no new semantic value beyond the schema.
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 clearly states it fetches one AIO paper by id, lists specific return contents (bilingual abstract, PDF URL, citation), and distinguishes it from siblings like list_papers which would list multiple papers.
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?
The description implies use when a specific paper id is known and full details are needed, and provides clear context. It doesn't explicitly mention alternatives or when-not-to-use, but the scope is clear.
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.