Skip to main content
Glama

SinoGreenTech Clean Energy

Get Structured Research Dossier from SinoGreenTech

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely useful behavior beyond that: automatic V2.1 Markdown/LaTeX serving, V1 HTML conversion fallback, and a tiered response where Free Trial yields only metadata/takeaways/preview while a Pro key yields the full dossier. It does not mention rate limits or error behavior for an unknown identifier.

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 compact sentences, front-loaded with the core action and identifier forms, followed by content-format and access-tier details. Minor waste in marketing-adjacent phrasing ('seamlessly', 'Automatically') that could be trimmed without loss.

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 one parameter, full schema coverage, and no output schema, the description covers what an agent needs: what comes back at each access tier and which full-text format to expect. It omits what happens on an unresolved identifier, which is the main remaining gap.

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% for the single 'identifier' parameter, and the description largely restates what the schema already documents (slug, DOI, numeric ID) rather than adding format constraints or precedence rules when an identifier could match multiple forms. Baseline 3 applies since the schema carries the semantics.

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?

States a specific verb ('Retrieve') and resource ('structured English research dossier for a specific paper') and enumerates the accepted identifier forms (slug, DOI, numeric ID). It does not explicitly name a sibling tool to contrast against, though the schema references search_research as the slug source, so it stops short of a 5.

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 by 'for a specific paper by slug, DOI, or numeric ID', and the schema hints that slugs come from search_research, but the description never states when to prefer this over search_research or extract_empirical_tables, nor any exclusion conditions. The tier note (Free Trial vs Pro) adds access context but not selection guidance.

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