eCFR

get_corrections

Read-only

Get editorial corrections for a CFR title, newest first.

Returns corrections with CFR references, corrective actions, error
dates, and FR citations, sorted by the date the error was corrected,
newest first. Useful for checking whether a section's current text has
been corrected since its last amendment.

section (e.g. '52.204-21'), part (e.g. '52') or chapter (e.g. '2' for
the DFARS) keeps only corrections that touch it. since_year keeps corrections with year >= since_year.
limit caps how many are returned (default 50, max 1000); truncated
says whether older ones were left out. Title 48 has ~280 corrections
since 2005.

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": "get_corrections"
  }
}

Input Schema

Name	Required	Description	Default
`part`	No
`limit`	No
`chapter`	No
`section`	No
`since_year`	No
`title_number`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: return fields, newest-first sorting, truncation behavior, default/max limits, and rough data volume for Title 48.

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 well structured and front-loads the purpose, followed by return details and filtering parameters. There is minor redundancy around 'newest first' and some return-field detail that the output schema may already cover.

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?

Given the output schema and annotations, the description is largely complete for a read-only retrieval tool with six parameters at 0% schema coverage. The main gaps are the undocumented title_number parameter and lack of explicit sibling-tool routing guidance.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden. It explains section, part, chapter, since_year, and limit with examples and semantics. It omits explicit documentation of title_number, though the title context and default 48 imply its role.

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?

The description states a specific verb and resource: 'Get editorial corrections for a CFR title, newest first.' It clearly distinguishes corrections from amendments but does not explicitly differentiate the tool from siblings such as find_recent_changes or get_version_history.

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?

It provides a clear use case: 'Useful for checking whether a section's current text has been corrected since its last amendment.' However, it does not name alternatives or state when not to use this tool versus sibling tools like find_recent_changes.

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

All eCFR 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.