Skip to main content
Glama

Get paper full text

get_paper_fulltext
Read-onlyIdempotent

Retrieve full text or specific sections of academic papers to verify claims or quote details. Use after searching for relevant papers.

Instructions

Use this when the user asks “what does the methods/results section say”, wants to quote a specific section, or when the abstract isn't enough to verify a claim. Heavy: only call once a paper looks relevant from search_papers, search_related_papers, or get_paper_citations. format=markdown returns one rendered document; format=json returns a structured section list. Pass sections (case-insensitive headings, e.g. ["Methods"]) to fetch only those sections instead of the whole document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNo`markdown` returns one rendered document, ready to read or quote inline. `json` returns a structured section list, useful when you want to navigate by section name (methods / results / related work).markdown
paper_idYesLune paper UUID, taken from a `search_papers`, `search_related_papers`, or `get_paper_citations` result.
sectionsNoReturn only these sections (case-insensitive heading match), e.g. ["Methods", "Results"]. Omit to return the whole document.
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds important behavioral context: the tool is 'heavy' (suggests constraint on number of calls) and explains the two output formats with their intended uses.

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?

Concise and well-structured. Every sentence adds value: use case, heavy warning, format explanation, section parameter. Front-loaded with purpose, then usage guidelines, then parameter details.

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?

Completeness is high given the tool's complexity (3 params, no output schema). It explains the heavy nature, section filtering, and format selection. Could be more explicit about exact output structure but current info is sufficient for a read tool.

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%, so baseline is 3. The description adds meaning: explains the difference between format values (markdown vs json), the purpose of sections (case-insensitive heading match), and where paper_id comes from (linked to other tools).

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 clearly states the tool's purpose: retrieving full text when abstract isn't enough or for quoting. It distinguishes from sibling search tools by specifying use cases and referencing `search_papers` etc. for obtaining the paper_id.

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?

Provides explicit when-to-use scenarios (abstract insufficient, quoting) and a strong usage guideline: 'only call once a paper looks relevant'. It does not explicitly name alternative tools but implies not to use for initial search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RetrogradeLabs/lune-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server