Skip to main content
Glama

get_paper

Read-onlyIdempotent

Full record for one paper: DOI (10.xxxx/..), PMID (digits) or PMCID (PMC...). Returns the abstract, open-access status and full-text links.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the description need not restate safety. It adds real value by disclosing the payload — abstract, open-access status and full-text links — which tells an agent what it will receive. Gaps remain around not-found/invalid-identifier behavior and whether paywalled records return partial data.

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, both earning their place: the first states scope and accepted input formats, the second states the return payload. The identifying information is front-loaded with zero filler.

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 required parameter, no output schema and full annotation coverage, the description supplies both the input formats and the returned fields. It is nearly complete; only failure modes (unknown DOI, unavailable full text) are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with a single generic "identifier" field, so the description carries the full burden and does it well, spelling out the three accepted identifier families (DOI 10.xxxx/.., numeric PMID, PMC-prefixed PMCID) with format examples. This is meaning an agent could not recover from the schema alone.

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 gives a specific verb+resource ("Full record for one paper") and immediately scopes it to lookup by DOI, PMID or PMCID, which clearly separates it from a search-style tool. It does not name a sibling such as search_literature, so it stops short of full differentiation.

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 this is the single-record retrieval path once it already has an identifier. There is no explicit "use this when..." statement nor any exclusion pointing to a search tool for unknown identifiers.

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