Skip to main content
Glama

SinoAILab AI & Robotics

Get Structured Research Dossier from SinoAILab

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 already establish readOnlyHint=true and openWorldHint=false, and the description adds real behavioral detail beyond that: automatic V2.1 Markdown/LaTeX serving, silent fallback conversion of V1 HTML, and tier-dependent response depth (metadata/takeaways/preview vs full dossier). It stops short of describing pagination, size limits, or error behavior for unknown identifiers.

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 no filler; the identifier forms and the version/tier behavior each get exactly one clause. Minor marketing adverbs ('seamlessly', 'Automatically') add little, but nothing is redundant enough to impede selection.

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 is largely sufficient: it explains the identifier input, the content versions returned, and how credentials change the payload. The one remaining gap is what happens when no dossier exists for the given identifier.

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% and the single identifier parameter already documents slug, DOI, and numeric ID forms. The description restates the same three forms without adding format rules, validation behavior, or examples beyond what the schema provides, so the baseline of 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 states a specific verb and resource ('Retrieve the structured English research dossier for a specific paper') and enumerates the three accepted identifier forms, so an agent knows exactly what this returns. It does not explicitly contrast itself with siblings like search_research or extract_empirical_tables, leaving that differentiation to inference from the resource name.

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?

The Free Trial vs Pro API key sentence implies context about what an agent will get depending on credentials, which is useful planning information. However, there is no explicit statement of when to prefer this tool over search_research or extract_empirical_tables, and no prerequisites or exclusions are given.

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