Lacuna Research MCP

get_paper

Read-onlyIdempotent

Fetches a Lacuna paper by artifact ID or URL, returning an agent-oriented context view with summary, authors, figures, and linked resources. Use it to retrieve paper details and related research.

Instructions

Fetch a Lacuna paper by artifact id or paper URL.

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.

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

Input Schema

TableJSON Schema

Name	Required	Default
`view`	No	context
`figure_limit`	No
`include_resources`	No
`artifact_id_or_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 21, 2026

addedInput schema / properties / include_resources

Added value: +{
+  "default": true,
+  "title": "Include Resources",
+  "type": "boolean"
+}

First observedv0.2.0Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses non-obvious behavior: include_resources defaults to True for context and full views, other views ignore it, figure_limit defaults to 3 server-side, and passing 0 suppresses previews while retaining a `figures_truncated` signal. It also explains that other versions require reading the returned version list's artifact ID.

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 one-line purpose, then a bulleted view breakdown that is scannable. It is somewhat long, and 'other views ignore this option' plus the include_resources explanation repeat the same default, but nearly every sentence carries usable routing detail.

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?

With an output schema present, the description need not explain return shapes, and it correctly focuses on view selection, defaults, and cross-tool handoff. For a 7-mode fetch tool, an agent has everything needed to pick a view and call it correctly.

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 all meaning, and it does: every enum value of `view` gets a definition and intended use, and both `include_resources` and `figure_limit` are explained with defaults and edge-case behavior. Only artifact_id_or_url is left to its name, which is self-evident.

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?

States a specific verb and resource ('Fetch a Lacuna paper') plus the accepted identifier forms (artifact id or paper URL). It also names 'get_resource' as the follow-up tool, so an agent can locate it against siblings like get_hypothesis or get_author_papers without opening a schema.

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?

Gives explicit routing: "context" is the default and recommended starting point "for almost everything," with per-view guidance on when to prefer full (cheaper, basic metadata), preview (citation display), and the single-field views. It also states the condition for switching views ('Pass a resource entry's id to get_resource').

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

Deploy Server