Skip to main content
Glama

SinoAgriTech Crop & AgriTech

Get Structured Research Dossier from SinoAgriTech

get_paper_dossier
Read-only

Retrieve the structured English research dossier for a specific paper by slug, DOI, or numeric ID. Automatically serves V2.1 Markdown/LaTeX full-text when available (or converts V1 HTML content seamlessly). Free Trial returns metadata, takeaways, and preview; Pro API key returns full dossier.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_paper_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesPaper slug (from search_research), DOI (e.g. "10.13929/..."), or numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses meaningful behavior: automatic version selection (V2.1 Markdown/LaTeX served, V1 HTML converted) and tier-dependent response depth (Free Trial = metadata/takeaways/preview vs Pro key = full dossier). It does not cover error behavior for unresolvable identifiers, but the version and tier disclosure is real added context.

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?

Three front-loaded sentences with the identifier forms and tier behavior placed early. Minor filler appears in words like 'seamlessly' and 'Automatically serves', but overall the text is dense and earns most of its space.

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 single-parameter read tool with no output schema, the description does an adequate job by describing what the return payload differs by tier (metadata/preview vs full dossier). Missing only failure modes and any note on identifier precedence when a value could match multiple forms.

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 coverage is 100% and the single identifier parameter is fully documented in the schema. The description restates the three accepted forms (slug, DOI, numeric ID) and adds only the minor hint that a slug can be sourced from search_research, so it does little beyond the schema.

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?

The definition opens with a specific verb and resource ('Retrieve the structured English research dossier for a specific paper') and enumerates the accepted identifier forms. It is clearly a fetch-by-identifier tool rather than a search, though it only implicitly separates itself from search_research by noting the slug comes from that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer it should call search_research first to obtain a slug, then use this tool to fetch the dossier. There is no explicit when-to-use/when-not-to-use guidance or mention of the sibling extract_empirical_tables or list_topic_hubs as alternatives.

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