Skip to main content
Glama

Get Paper

get_paper
Read-onlyIdempotent

Fetch a specific paper's summary, authors, figures, or full text by artifact ID, arXiv ID, DOI, or URL. Use after a search or when a user names a paper.

Instructions

Fetch one paper: its summary, authors, venue, figures, linked resources, or full text.

Accepts a Lacuna artifact ID or paper URL from search_lacuna, or an outside identifier for the same paper: an arXiv ID (2310.06825), a DOI, or an arXiv, DOI or OpenReview URL. Use this when the user names a specific paper or after a search. For an outside identifier that is not in Lacuna's ML/AI corpus, the result is found: false with a note saying so. The default view is a summary; ask for the full text only when the summary does not answer the question.

include_resources adds linked resources (code repositories, datasets, models, and demos) in context and full views by default. Pass False to omit them; other views ignore this option. Pass a resource entry's id to get_resource for further details.

view selects the response shape. context requests Lacuna's compact agent-oriented context by default, while the four single-field views (blog/figures/concepts/neighbors) return isolated sub-resources:

  • "context" (default, recommended): agent-oriented summary with summary_markdown, authors, and a small figure preview. Start here for almost everything. Available versions are included when present; to read another version, use its artifact ID from the returned version list.

  • "full": raw upstream paper record. Cheaper than context when you only need basic metadata.

  • "preview": compact card with unique fields excerpt, excerpt_kind, bookmarked. Use for citation-style display.

  • "blog": just the summary_markdown content, without the rest of the context envelope.

  • "figures": just the figures list.

  • "concepts": just the concepts list.

  • "neighbors": just the related-papers list.

  • "fulltext": the paper itself, max_chars at a time (default 40,000, at most 100,000) from offset; pass the returned next_offset to keep reading. format says what you got: "latex" is the arXiv LaTeX source without its bibliography (citations appear as \cite keys); "pdf_text" is text extracted from the PDF, where equations and tables can be garbled. A scanned paper has no text.

figure_limit (context view only) caps the figure preview (server default 3). Pass 0 to suppress figure previews while keeping a figures_truncated signal.

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

Input Schema

NameRequiredDescriptionDefault
viewNocontext
offsetNo
max_charsNo
figure_limitNo
include_resourcesNo
artifact_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.11
    • addedInput schema / properties / max_chars
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Max Chars"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "context",
      -  "full",
      -  "preview",
      -  "blog",
      -  "figures",
      -  "concepts",
      -  "neighbors"
      -]New value: +[
      +  "context",
      +  "full",
      +  "preview",
      +  "blog",
      +  "figures",
      +  "concepts",
      +  "neighbors",
      +  "fulltext"
      +]
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / include_resources
      Added value: +{
      +  "default": true,
      +  "title": "Include Resources",
      +  "type": "boolean"
      +}
  3. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses out-of-corpus behavior (found: false with a note), fulltext paging semantics with next_offset, format values (latex vs pdf_text with citation/equation caveats), the no-text case for scanned papers, and the figures_truncated signal when figure_limit is 0. This is exactly the behavioral context an agent needs and that annotations cannot carry.

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 core action and usage condition, then organized as a scannable per-view list that matches the eight-value enum. It is long, but the length is justified by the view matrix; a few clauses (e.g., "other views ignore this option") could be tightened without loss.

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

Completeness5/5

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

For a six-parameter tool with an eight-way view enum and an output schema, the description covers identifier acceptance, view selection, paging, and failure modes. Nothing an agent needs in order to call it correctly is missing, and the added return-shape notes are a bonus rather than a necessity.

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 description coverage is 0%, so the description must carry the load, and it does: every view enum member is defined, include_resources is scoped to context/full views, figure_limit is scoped to context view with its default and 0-suppression behavior, and offset/max_chars are explained for fulltext with size limits. The only small friction is the stated 40,000 max_chars default versus the schema's null default, but the intent (server default) is recoverable.

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?

"Fetch one paper" is a specific verb+resource, immediately expanded to what is returned (summary, authors, venue, figures, resources, full text). It clearly distinguishes itself from search_lacuna by accepting a single known identifier rather than a query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call it: "when the user names a specific paper or after a search," which routes the agent correctly relative to search_lacuna. It also gives per-view guidance, including "Start here for almost everything" for context and "ask for the full text only when the summary does not answer the question," plus a handoff to get_resource for resource detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.