Skip to main content
Glama
Sign In
nara-catalog-mcp

nara-catalog-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_comments

Read-only

Find National Archives Catalog records other researchers commented on, filtered by record ID, contributor, or comment words. Use these comments as leads, not verified NARA findings.

Instructions

Find records other researchers have commented on.

Useful for picking up where someone else stopped: a comment naming a surname often marks a file that a researcher has already read. Unverified by NARA, so it points at records rather than settling anything.

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_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
naidNoRestrict to comments on one record.
pageNoPage of results, 1-based.
limitNoMaximum records to return (1-100).
queryNoWords to find in comments.
contributorNoRestrict to one contributor's screen name.

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

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world safety profile, but the description adds real context beyond them: comments are community-contributed and "unverified by NARA," so results are leads rather than authoritative facts. That trust caveat is exactly the kind of behavioral disclosure annotations cannot convey.

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?

Three sentences, front-loaded with the core purpose, and each adds something (use scenario, trust caveat). The middle illustrative sentence about surnames is slightly long but still earns its place by explaining why the tool is worth calling.

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

Completeness4/5

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

For a five-parameter read-only search with no output schema, the description covers purpose, value, and data trustworthiness adequately. It stops short of describing the shape of returned records, but no output schema exists and the parameters are fully documented elsewhere.

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%, so every parameter (naid, page, limit, query, contributor) is already documented in the schema. The description only loosely implies full-text matching on comments via the surname example and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — find records that have been commented on — which clearly distinguishes the output (records) from get_comments (the comments themselves). It does not name any sibling by name, so an agent must infer the boundary against search_records or search_by_contribution_text.

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?

"Useful for picking up where someone else stopped" gives a concrete use scenario rather than leaving usage implicit. However, no exclusions or explicit alternatives (e.g. when to prefer this over search_records or get_comments) are stated.

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