Skip to main content
Glama

SinoTechIntel Materials & Tech

Get Structured Research Dossier from SinoTechIntel

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?

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context beyond them: automatic V2.1 Markdown/LaTeX full text, fallback conversion of V1 HTML, and the tiered response depth (Free Trial = metadata, takeaways, preview; Pro key = full dossier). Missing only latency or rate-limit behavior.

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 short sentences, front-loaded with the core action, then delivery behavior, then tiering. Every sentence carries information; the only mild redundancy is repeating the identifier forms already present in the schema.

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 one-parameter read tool with no output schema, the description covers identification, content served, fallback conversion, and what differs between free and paid access. An agent has enough to call it correctly, though it does not say what happens on an unknown identifier or when content is unavailable in either version.

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%, so the single 'identifier' parameter is already fully documented in the schema, including the DOI example. The description restates the same three accepted forms without adding format or validation detail beyond the schema, so baseline 3 applies.

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 description uses a specific verb and resource ('Retrieve the structured English research dossier for a specific paper') and enumerates the three identifier forms (slug, DOI, numeric ID). It is clearly distinct from search_research in intent, though it never names a sibling to contrast against.

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 context is implied rather than stated: an agent can infer this is the fetch-after-search step, and the schema note that the slug comes 'from search_research' reinforces that. However, there is no explicit when-to-use/when-not guidance and no mention of when to prefer extract_empirical_tables or list_topic_hubs instead.

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