Skip to main content
Glama
Sign In

Federal Register

by com.1102tools
OverviewDiscussionsAdmin

get_document

Read-only

Get full details for a single Federal Register document by number.

Returns all available fields including full text URLs, docket info, RIN details, page views, topics, corrections, and CFR references.

Document numbers look like '2026-03065' (modern), 'E9-12940' or 'X94-70302' (legacy pre-2011 archive), or 'C1-2026-01234' (corrections).

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_number": "<document_number>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description doesn't need to repeat it. It adds real context beyond that: the breadth of returned fields (full text URLs, docket, RIN, corrections, CFR refs) and the existence of legacy and correction identifiers that behave differently. It does not cover error behavior for an invalid number, which keeps it below a 5.

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

Conciseness5/5

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

Three short blocks, front-loaded with purpose, then return scope, then the identifier format that an agent must get right before calling. No sentence is filler; the legacy-archive note in particular is load-bearing rather than decorative.

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?

With an output schema present the description needn't enumerate return values, and annotations cover the safety profile; between them an agent has enough to call correctly. The only gap is behavioral edge cases — what happens on an unknown or malformed document number — which is minor for a read-only single-record fetch.

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 coverage is 0% — the single parameter has no description at all — so the description carries the full burden, and it does: it specifies the exact shape of valid values and gives concrete examples across modern ('2026-03065'), legacy ('E9-12940', 'X94-70302') and correction ('C1-2026-01234') formats. That is meaningful semantics the schema alone does not supply.

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 (get full details for a single Federal Register document) and scopes it to retrieval by number, which implicitly separates it from the list/batch siblings. An agent can tell this is the single-record fetch versus get_documents_batch or search_documents without opening any schema.

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?

The phrase 'a single ... document by number' establishes clear context: use this when you already have one identifier, not a query. It stops short of explicitly naming search_documents as the way to obtain a number or get_documents_batch for multiple documents, so the routing is inferred rather than stated.

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

All Federal Register toolsInspect
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.

Resources