nara-mcp-server

Search National Archives records

search_records

Search the US National Archives Catalog for historical records by query, title, identifier, date range, or media type.

Instructions

Search the US National Archives Catalog records endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_records"
  }
}

Input Schema

Name	Required	Description
`query`	No	Full-text query passed as q.
`title`	No	Title search filter.
`naId`	No	National Archives Identifier search filter.
`level`	No	Description level, such as item, fileUnit, series, or recordGroup.
`online`	No	Limit to records with online objects.
`objectType`	No	Object type filter, such as photograph, map, or text.
`startDate`	No	Start date filter accepted by the Catalog API.
`endDate`	No	End date filter accepted by the Catalog API.
`availableOnline`	No	Alias for online when a client prefers clearer wording.
`limit`	No	Number of results to return.
`page`	No	Result page.
`sourceIncludes`	No	Comma-separated source fields to include.
`abbreviated`	No	Request abbreviated records where supported.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the endpoint and lacks information on authentication, rate limits, pagination behavior, or response structure, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is overly terse for a tool with 13 parameters and no annotations. While front-loaded, it omits critical details and does not earn its place by providing sufficient information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks completeness given the tool's complexity (13 parameters, no output schema, no annotations). It fails to cover use cases, prerequisites, or outcome expectations, making it hard for an agent to use correctly.

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 input schema has 100% description coverage for all 13 parameters, so the schema itself documents parameters well. The description adds no new meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool searches the US National Archives Catalog records endpoint, identifying the specific resource and action. However, it does not differentiate from sibling tools like get_record for specific records or catalog_request for other endpoints.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_record or get_child_records. The agent is left to infer usage without context on filtering versus specific record retrieval.

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

Deploy Server