Skip to main content
Glama
Sign In

Lacuna Research MCP

by io.github.tiptreesystems
OverviewDiscussionsAdmin

Get Paper

get_paper
Read-onlyIdempotent

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

NameRequiredDescriptionDefault
viewNocontext
figure_limitNo
include_resourcesNo
artifact_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: default view, per-view return shapes, that non-context views ignore include_resources, and that figure_limit=0 still emits a figures_truncated signal. It stops short of pagination or error behavior.

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?

Front-loaded with purpose, then structured bullets per enum value; the length is justified by seven view options that each need disambiguation. Sentences are dense with information rather than filler.

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?

Even though an output schema exists and annotations cover safety, the description explains what each response shape contains and the defaults/truncation signals an agent needs. Nothing required to call it correctly is missing.

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 description coverage is 0%, so the description must carry all parameter meaning, and it does so well for view (each of the 7 enum values explained), include_resources (default true, effect per view, False behavior), and figure_limit (default 3, 0 semantics). The required artifact_id_or_url is only lightly characterized, with no format guidance for id vs URL.

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 opening line states a specific verb and resource ('Fetch a Lacuna paper by artifact id or paper URL') and the rest of the description makes the tool's scope unmistakable versus siblings like get_resource and search_lacuna. An agent can distinguish it without opening any schema.

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?

Gives concrete selection guidance within the tool ('context': 'Start here for almost everything'; 'full': 'Cheaper than context when you only need basic metadata') and routes the agent to get_resource for resource detail. It does not, however, say when to prefer get_paper over siblings such as search_lacuna or get_author_papers.

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

All Lacuna Research MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources