libofcongress-mcp-server

Get Newspaper Page

libofcongress_get_newspaper_page

Read-only

Retrieve the full OCR text of a specific historical newspaper page along with publication metadata. Pass the url field from a libofcongress_search_newspapers result — do not construct this URL manually. OCR quality varies by digitization batch and era: 19th-century and degraded materials may contain fragmented text, garbled words, and line-break artifacts that are surfaced as-is. When a page exists but has no digitized text, ocr_available is false and ocr_text is empty — this is a data property, not an error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page_url`	Yes	The url field from a libofcongress_search_newspapers result (e.g., "https://www.loc.gov/resource/sn83045462/1905-03-15/ed-1/seq-1/"). Always pass the value directly from search results — do not construct or modify this URL.

Output Schema

TableJSON Schema

Name	Required	Description
`date`	No	Issue publication date.
`error`	No	Present when the call failed. Absent on success.
`state`	No	State where the newspaper was published.
`notice`	No	Set when ocr_available is true but ocr_text is empty — the page has digitized OCR, but the text service did not return it this call. Distinguishes a transient retrieval miss from a genuinely image-only page (where ocr_available is false). Absent when OCR text was returned or the page has no OCR.
`edition`	No	Edition or publication context identifier.
`ocr_text`	No	Full plain-text OCR content for the page. Empty string when ocr_available is false. May contain fragmented words, line-break artifacts, and misspellings inherent to historical OCR — do not attempt to repair.
`page_url`	No	The LOC resource URL for this newspaper page.
`sequence`	No	Page sequence number within the issue.
`ocr_available`	No	True when digitized OCR text exists for this page. False for image-only digitization batches where OCR has not been applied.
`newspaper_title`	No	Title of the newspaper publication.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: OCR quality varies by batch/era, text may be fragmented or garbled, and missing OCR is represented as ocr_available=false with empty ocr_text and is explicitly not an error. This preempts likely misinterpretations by the agent.

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 focused sentences with no filler. The primary purpose is front-loaded, the critical usage constraint is stated early, and the edge-case behavior is placed at the end without bloating the description.

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 single-parameter read-only retrieval tool with an output schema and 100% schema coverage, the description covers everything needed: what is retrieved, how to obtain the URL, likely data-quality issues, and how to interpret empty OCR results. No essential guidance 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 coverage is 100%, and the schema already documents the page_url parameter, including an example and an explicit warning not to modify the URL. The description reinforces the same guidance but adds no new semantic information beyond the schema, matching the baseline for full 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?

The description opens with a specific verb and resource: 'Retrieve the full OCR text of a specific historical newspaper page along with publication metadata.' This clearly distinguishes it from the sibling search/browse tools and leaves no ambiguity about what the tool returns.

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?

The description gives clear operational context by instructing the agent to pass the url field from a libofcongress_search_newspapers result and not to construct the URL manually. It implies the correct workflow, though it does not explicitly contrast this tool with siblings such as libofcongress_get_item.

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

All libofcongress-mcp-server tools Inspect

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.