lantern-mcp

get_lantern_text

Retrieve full OCR text for any leaf, returning a cached file path for reading or grepping the entire page when search excerpts are insufficient.

Instructions

Download one leaf's OCR text, returning the path to the cached file.

Use only when the search excerpt is not enough and the whole page has to be read or grepped. This is expensive per volume: the Internet Archive serves OCR per volume rather than per page, so the first leaf of a volume costs an 8-25 MB download and every later leaf of that volume is then free.

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": {
      "reference": "<reference>"
    },
    "name": "get_lantern_text"
  }
}

Input Schema

Name	Required	Description	Default
`reference`	Yes	Leaf reference, as returned by `search_lantern`

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Discloses per-volume cost and caching behavior: first leaf triggers 8-25 MB download, subsequent leaves free. This goes beyond the basic 'download' description and informs decisions, especially since no annotations are provided.

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?

Two concise sentences, first states action, second provides guidance. No fluff, efficient.

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?

For a simple one-parameter tool with output schema, the description covers purpose, usage criteria, cost behavior, and return value. No missing critical information.

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?

The single parameter 'reference' is fully described in schema (100% coverage) including provenance from search_lantern. Description adds no extra semantic beyond schema, but that's unnecessary due to high schema coverage.

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?

Clear verb 'Download', specific resource 'one leaf's OCR text', and explicit outcome 'path to cached file'. Distinguishes from sibling search_lantern by focusing on whole-page download vs excerpts.

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?

Explicit 'Use only when...' with condition 'search excerpt is not enough and whole page has to be read or grepped'. Also mentions cost trade-off, guiding when to prefer this over search.

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

Deploy Server