Skip to main content
Glama

get_paper

Fetch one paper by id, with full abstract and PDF link.

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": {
      "paper_id": "<paper_id>"
    },
    "name": "get_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoarxiv
paper_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does add real value by saying the response includes the full abstract and a PDF link, and "Fetch" implies a non-mutating read, but it says nothing about behavior for unknown ids, missing abstracts, or what the source parameter changes.

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?

A single front-loaded sentence with the resource first and the return payload second; no filler and nothing buried.

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?

This is a low-complexity single-record read with no output schema and no annotations, and the description covers purpose plus the main return contents. The remaining hole is the undocumented source parameter, which is the only meaningful gap for a tool this simple.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters depend on the description. "by id" loosely covers paper_id, but the source parameter (default "arxiv", a free-form string with no enum) is left entirely unexplained in both schema and description, leaving the agent to guess valid values.

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?

"Fetch one paper by id" names a specific verb and resource, and the word "one" distinguishes it from batch/single-collection siblings like get_papers_batch and get_paper_authors. It stops short of naming an alternative outright, so the differentiation is implicit rather than explicit.

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: the agent must already hold a paper id, which is signaled by "by id" and the required paper_id parameter. There is no statement about when to prefer read_paper or get_papers_batch, and no preconditions or failure behavior are described.

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.