Skip to main content
Glama

SinoBioData Biomedical Research

Get Structured Research Dossier from SinoBioData

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

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real substance beyond them: automatic serving of V2.1 Markdown/LaTeX, seamless fallback conversion of V1 HTML, and tiered behavior where a Free Trial returns metadata/takeaways/preview versus a Pro API key returning the full dossier. That tells an agent both what content comes back and what credentials change the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and resource, then the fallback/format behavior, then access tiers. No filler and no repetition beyond the parameter forms that also serve as a quick reminder.

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?

With no output schema, the description usefully covers content formats, V1-to-V2.1 conversion, and what each access tier returns, which is what an agent needs to decide feasibility. It stops short of describing failure behavior for an invalid or ambiguous identifier (slug colliding with numeric ID) or the size/shape of a 'dossier'.

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, including the DOI example. The description restates the same three identifier forms and adds only the provenance note that slugs come from search_research, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource: 'Retrieve the structured English research dossier for a specific paper', with the accepted identifier forms (slug, DOI, numeric ID) stated up front. This clearly separates it from search_research (which it references as the source of slugs) and from extract_empirical_tables/list_topic_hubs, which act on different resources.

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 only implied: mentioning 'Paper slug (from search_research)' hints at the search-then-fetch workflow, and the Free Trial vs Pro line hints at access prerequisites. There is no explicit when-to-use statement, no when-not-to-use, and no stated alternative for cases where a full dossier is not wanted.

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