Skip to main content
Glama
ianderso

nara-catalog-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_record_images

Read-only

List a record's page images in page order with their object IDs, providing evidence to read before citing the record. Use the IDs or page numbers to download images.

Instructions

List a record's page images in page order, each with its object id.

These are the evidence. A catalog description summarises a file; it does not tell you what any individual page says, so read the images before citing anything to this record. The object id is what get_extracted_text and get_transcriptions entries point at; pass it, or the page number, to download_page_image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
naidYesThe record's NAID.
refreshNoTrue re-reads from the Catalog instead of the cache, spending one call and replacing the cached copy. The cache never expires on its own, so use this when the answer may have changed since you last asked.

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.4/5.0
Behavior4/5

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

Annotations (readOnlyHint, openWorldHint) already cover the safety profile, so no contradiction risk. The description adds the read-only role of this output as 'the evidence' and its linkage to other tools. Caching/refresh behavior is disclosed in the schema, not the description, leaving only a minor gap.

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?

Front-loaded with the return shape, followed by the why-this-matters rationale and the cross-tool linkage. Slightly prose-y in the middle sentence but each sentence carries information.

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?

There is no output schema, so the description must carry the return-value burden, and it does: page order plus per-page object id. Combined with annotations and a fully documented schema, an agent has everything needed to call and use this tool.

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 itself richly documents both naid and the refresh/cache semantics, so the baseline is 3. The description clarifies that the returned object id is the value other tools consume, but it adds nothing about the parameters' own syntax or defaults.

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+resource+scope: 'List a record's page images in page order, each with its object id.' An agent knows exactly what it gets back and how it differs from generic record fetchers like get_record.

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 workflow guidance: 'read the images before citing anything to this record,' plus the fact that catalog descriptions don't capture individual page content. It names the downstream siblings (get_extracted_text, get_transcriptions, download_page_image) and the condition for using each via the object id or page number.

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