Skip to main content
Glama

federal-regulations-mcp-server

by io.github.cyanheads

regulations_get_document

regulations_get_document
Read-onlyIdempotent

Fetch one Federal Register document by its FR document number — full metadata (title, type, agencies, abstract, action, effective/comment dates, RINs) plus the cross-source handles that make this a workflow server. The output carries the docket ID (chain into regulations_get_docket or regulations_find_comments) and the affected CFR parts (chain into regulations_get_cfr_section). Set include_full_text only when the rule body itself is needed — final rules can run tens of thousands of words.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_numberYesFederal Register document number (e.g. "2025-14555"). Obtain from regulations_search_rules results (the documentNumber field).
include_full_textNoWhen true, fetch and inline the document body as plain text (can be large). Default false returns the body URLs only; fetch full text only when you need to read the rule itself, not just its metadata and cross-links.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoDocument type.
datesNoFree-text dates summary from the rule, or null.
errorNoPresent when the call failed. Absent on success.
titleNoDocument title.
actionNoAction line (e.g. "Final rule."), or null.
htmlUrlNoFederal Register web URL for the document.
abstractNoAbstract summary, or null.
agenciesNoIssuing agency names.
docketIdNoRegulations.gov docket ID — chain into regulations_get_docket / find_comments. Null when not on Regulations.gov.
fullTextNoInlined plain-text body — present only when include_full_text=true.
rawTextUrlNoURL of the plain-text body.
bodyHtmlUrlNoURL of the rendered HTML body.
effectiveOnNoEffective date (ISO 8601), or null.
commentCountNoFR-reported comment count from Regulations.gov; null when not on Regulations.gov.
cfrReferencesNoAffected CFR parts — chain into regulations_get_cfr_section.
documentNumberNoFederal Register document number.
commentsCloseOnNoComment-period close date (ISO 8601); when set, still open for comment.
publicationDateNoPublication date (ISO 8601).
regulationIdNumbersNoRegulation Identifier Number(s) (RIN).
supportingDocumentsNoRelated Regulations.gov supporting documents.
regulationsGovDocumentIdNoRegulations.gov document ID — chain into regulations_find_comments (document-scoped). Null when absent.

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, and the description adds concrete behavioral detail: default returns body URLs only, include_full_text fetches the body which 'can run tens of thousands of words', and the output carries docket ID and CFR parts. This goes beyond the annotations and helps the agent anticipate payload size and output structure.

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?

Two sentences with each serving a distinct purpose: core fetch, workflow chaining, and the include_full_text caveat. The information is front-loaded and there is no redundant wording.

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?

For a two-parameter, read-only tool with a rich output schema, the description supplies the operational essentials: what the metadata covers, what cross-links are available, and when to request full text. Nothing an agent needs to invoke it correctly is omitted.

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?

Both parameters are fully documented in the schema (100% coverage) with examples and guidance, so the description is not required to carry the load. It does add context around include_full_text (size warning, metadata-only default) and document_number sourcing via search_rules, but these are also present in the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Fetch one Federal Register document by its FR document number') and enumerates the returned metadata. It differentiates from siblings by describing the cross-source handles and chaining targets (regulations_get_docket, regulations_find_comments, regulations_get_cfr_section), making clear this is the document-level entry point.

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 description gives usage context by telling the agent to chain into regulations_get_docket, regulations_find_comments, or regulations_get_cfr_section when those are the downstream need, and advises to set include_full_text only when the rule body is needed. It does not explicitly state when not to use this tool versus alternatives, but the chaining instructions and full-text warning provide clear context.

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

All federal-regulations-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: browsing vs searching, getting specific entities (CFR sections, dockets, documents) vs listing/finding comments. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the consistent 'regulations_<verb>_<object>' pattern (e.g., browse_cfr, get_docket, list_open_comments), making it easy to predict functionality.

Tool Count5/5

Seven tools is well-scoped for a regulations domain, covering discovery (search, browse, list) and retrieval (get, find) without redundancy or bloat.

Completeness5/5

The set covers the core regulatory workflow: searching rules, browsing CFR structure, retrieving specific sections, dockets, documents, and comments. No obvious gaps for read-only access.

Resources