Federal Register

get_documents_batch

Read-only

Fetch multiple documents in one call (up to ~20).

Pass a list of document numbers to fetch up to about 20 in one call.
Always returns {count, results, [errors]}; errors.not_found lists any
requested numbers the API could not locate. Results come back in the
order requested. Image metadata (images, images_metadata) is left out
to keep batches small; get_document returns it.

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": {
      "document_numbers": "<document_numbers>"
    },
    "name": "get_documents_batch"
  }
}

Input Schema

Name	Required	Description	Default
`document_numbers`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint=false, and the description adds real behavioral context on top: partial-failure handling via errors.not_found instead of whole-batch failure, preserved result ordering, and deliberate omission of image payloads to keep batches small.

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 core action and cap, then organized into input, return shape, and omission notes. Minor waste: the ~20 limit is stated twice (headline and body).

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?

Despite a simple one-parameter shape, the description covers the cap, ordering guarantee, partial-failure semantics, and the cross-reference for omitted fields. Return-value explanation partly duplicates the output schema, but that costs conciseness rather than completeness.

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

Parameters5/5

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

Schema description coverage is 0% with one undocumented array parameter, so the description carries the burden and does: it specifies the parameter is a list of document numbers, the ~20 cap, and that output order follows request order. This is meaning well beyond the bare 'array of string' schema.

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 and resource with batch scope: 'Fetch multiple documents in one call (up to ~20)'. An agent can immediately distinguish it from the single-document get_document sibling and from search_documents.

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?

Explicitly routes the agent to get_document when image metadata (images, images_metadata) is needed, and the 'multiple in one call' framing implies the alternative for single fetches. It lacks an explicit exclusion for search-style retrieval, so it stops short of full when/when-not coverage.

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

All Federal Register tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.