Skip to main content
Glama
ianderso

nara-catalog-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_page_image

Idempotent

Download a page image from a US National Archives Catalog record to a local file for reading or evidence. Specify NAID, page or object_id, and destination path.

Instructions

Download one page of a record so it can actually be read.

This is the step that turns a catalogue hit into evidence. The image is written to disk rather than returned inline — a page scan runs to several megabytes.

NARA's media URLs are open and need no key, so this costs nothing against your API allowance. One catalogue call resolves the page list; the download itself is not an API call.

A pension file can run to sixty pages and the page you need is rarely the first. Use get_extracted_text or get_transcriptions to find which page carries the fact, then fetch it by the object_id they name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
naidYesThe record's NAID, e.g. '54765873'.
pageNoWhich page to download, 1-based, in the order get_record_images lists them. Defaults to 1 when object_id is not given.
object_idNoThe digital object to download, as get_extracted_text, get_transcriptions and get_record_images name it. An alternative to page: pass one or the other.
destinationYesAbsolute path of a new file to write, e.g. '/tmp/hall-w17050-p51.jpg'. The directory must already exist, and the file must not: nothing is ever overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The annotations correctly indicate a non-read-only, open-world, idempotent, and non-destructive operation. The description adds significant value beyond this by explaining that the output is written to disk (not returned inline), that it doesn't count against API limits, and that it requires an existing directory and a new file path. This is rich behavioral context that an agent needs.

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?

The description is concise and front-loaded, with the core action stated in the first sentence. However, the final paragraph about typical file sizes and the need to find the right page could be considered slightly extraneous, though it's useful context. Overall, it's well-structured.

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?

Given the tool's complexity (file download) and the lack of an output schema, the description covers all necessary aspects: where the file is written, prerequisites (directory existence, no overwriting), cost, and how to obtain the necessary identifiers. It is complete for an agent to use the tool correctly.

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?

With 100% schema description coverage, the schema already defines each parameter. The description adds usage context by implying that 'page' and 'object_id' are alternatives and that 'page' is 1-based (matching the schema). It doesn't add new syntax details, but it reinforces how to obtain the 'object_id' from other tools, which is valuable.

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 (download), resource (one page of a record), and outcome (written to disk, not returned inline). It clearly distinguishes itself from sibling read tools like get_extracted_text or get_transcriptions by describing the physical file download.

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?

Provides explicit guidance on when to use this tool: it explains that you should first use get_extracted_text or get_transcriptions to identify the correct page, and then use this tool to fetch it. It also notes that the page needed is rarely the first in a large file, which provides useful context for usage.

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