nara-mcp-server

Get child records

get_child_records

Fetch records whose parent is the given National Archives Identifier. Supports pagination and limiting results.

Instructions

Fetch records whose parent is the supplied National Archives Identifier.

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": {
      "parentNaId": "<parentNaId>"
    },
    "name": "get_child_records"
  }
}

Input Schema

Name	Required	Description
`parentNaId`	Yes	Parent National Archives Identifier.
`limit`	No
`page`	No
`sourceIncludes`	No	Comma-separated source fields to include.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Fetch records' without revealing pagination behavior (limit/page parameters exist but unanswered), error handling, response format, or any side effects. The minimal description fails to provide expected behavioral context.

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 remarkably concise at one sentence. It front-loads the key action and resource. While very efficient, it could be slightly expanded without harming conciseness.

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 tool has 4 parameters and no output schema. The description omits important context like pagination, field inclusion (sourceIncludes), result limits, and relationship to sibling tools. It is insufficiently complete for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (parentNaId and sourceIncludes have descriptions; limit and page lack descriptions). The description adds no parameter-level detail beyond what the schema already provides. For low coverage, description should compensate but does not.

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 clearly states the action ('Fetch records') and the specific condition ('whose parent is the supplied National Archives Identifier'). It effectively differentiates from sibling tools like get_record (single record) and search_records (search across records).

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

Usage Guidelines3/5

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

The description implies usage when needing child records of a parent NaId, but lacks explicit guidance on when not to use or alternatives. No mention of prerequisites or fallback tools.

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

Deploy Server