Skip to main content
Glama

PaperList

Get paper

get_paper
Read-onlyIdempotent

Get one paper's full record by id (e.g. iclr2026-1058, paper-1058, iclr2027-n42, a numeric catalog id, a paperlist.ai paper URL, or an OpenReview forum id if it is in Paperlist), including the review summary or ICLR 2027 TLDR when available. Slug ids are verified against venue and year, so iclr2026-1 will not silently return an unrelated paper-1.

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

Input Schema

NameRequiredDescriptionDefault
idYesPaper id from search results

Output Schema

NameRequiredDescriptionDefault
noteNo
paperYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: slug ids are verified against venue and year, so a mismatched id (iclr2026-1) will not silently resolve to an unrelated paper-1, and it states the payload includes review summaries or the ICLR 2027 TLDR when available.

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?

Two sentences, front-loaded with the action and resource, with no filler. The long inline list of id formats is dense but each item is actionable; it could be split into a short lead plus examples for easier scanning.

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?

An output schema exists, so return values needn't be described. Between the id-format enumeration, the verification guarantee against slug mismatches, and the note about which supplementary content may be present, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline would be a 3. The description goes beyond the terse schema hint by enumerating accepted id forms: venue slugs, raw paper slugs, numeric catalog ids, paperlist.ai URLs and OpenReview forum ids, which directly affects what an agent can pass.

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?

The description opens with a specific verb and resource: 'Get one paper's full record by id.' Explicitly scoped to a single record, which cleanly separates it from the list_/search_ siblings that return multiple papers.

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

Usage Guidelines4/5

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

The schema's id hint ('Paper id from search results') and the format examples make it clear that this tool is used after discovery, to resolve one known id. It doesn't name search_papers or search as the alternative for discovery, so the routing is implied rather than stated.

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