Skip to main content
Glama

read_paper

Read a paper's full text. format='markdown' (default, body with formulas as $LaTeX$), 'html' (raw LaTeXML HTML), or 'latex' (the original LaTeX manuscript from the e-print source). arXiv only; id like 2401.01234.

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

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown
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?

With no annotations, the description carries the full behavioral burden; it does disclose that 'latex' returns the original manuscript from the e-print source and that the tool is arXiv-scoped, which is useful. It says nothing about failure modes, missing sources, response size or truncation for very long papers.

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?

Front-loaded with the purpose, then format options, then the arXiv/id constraint; every clause carries information. The telegraphic style ("arXiv only; id like 2401.01234") is dense but slightly clipped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no annotations and no output schema, the format semantics are adequately explained, but the return shape (size, structure, whether the markdown body is the whole paper) and the undocumented source parameter leave real gaps.

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 0%, so the description must compensate. It does well for paper_id (id format example) and format (three named values, default, and what each returns), but the source parameter is only obliquely covered by "arXiv only" and is never named or described.

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?

"Read a paper's full text" is a specific verb+resource and the emphasis on full text implicitly separates it from metadata-style siblings like get_paper. It stops short of naming any alternative, so differentiation is inferred rather than stated.

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?

Gives an eligibility constraint ("arXiv only") and a valid id form, which helps an agent decide whether it can call the tool at all. It never says when to prefer this over get_paper or extract_pdf, nor what to do for non-arXiv papers.

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.