Skip to main content
Glama
Sign In
litreview-mcp

litreview-mcp

by ajbraus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Find open-access PDF

find_open_pdf
Read-only

Locate a free, legal copy of a scholarly paper by DOI or OpenAlex ID. Returns a direct PDF or online-reading link, or null when only a paywalled version is known; check version differences.

Instructions

Find a free, legal copy of a paper. Returns a direct pdf_url when one is known, and otherwise a read_online_url. Both are null if no open copy is known, in which case the paper is probably paywalled. Check the version field: a preprint can differ from the published paper.

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": "find_open_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOpenAlex ID (W2057673348) or DOI (10.1207/s15326985ep4102_4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. Beyond that, the description discloses the return contract — direct pdf_url when known, otherwise read_online_url, both null when no open copy exists — and warns that the version field may reference a preprint rather than the published paper. It omits any mention of source coverage or latency, which keeps it below a 5.

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?

Three short sentences, front-loaded with the purpose, then the return shape, then the caveat about versions. Every sentence carries information an agent needs and there is no filler.

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?

With no output schema, the description correctly carries the burden of explaining return values, including the null-means-paywalled inference. For a one-parameter read-only lookup this is nearly complete; only a pointer to the sibling get_paper for metadata is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single id parameter already documents both accepted formats (OpenAlex ID and DOI) with examples. The description adds nothing about the identifier, so the schema baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Find a free, legal copy of a paper") and makes the output distinction explicit (pdf_url vs read_online_url). It does not name the sibling get_paper or explain why an agent would pick this over it, so differentiation is only implicit.

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

Usage Guidelines3/5

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

The intent is implied — use this when you want an accessible full text — but there is no explicit when-to-use/when-not guidance relative to get_paper or search_papers. The note about nulls implying a paywall is interpretation guidance for the result, not invocation guidance.

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

Deploy Server

Other Tools