Skip to main content
Glama

Search or read US Code of Federal Regulations sections

law_ecfr
Read-only

Searches the US eCFR by keyword or retrieves the current text of a specific section (title, part, section) via the official eCFR API. Returns hierarchy, heading, text (max 50,000 characters), last amended date, and official URL. Coverage: current CFR as published on ecfr.gov. Related tools on this server, for a different need: law_federal_register when you need to search Federal Register documents by term or agency. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeyword search query (max 200 characters)
partNoCFR part number (e.g. 1020) for section lookup
limitNoMax search results (1–25, default 10)
titleNoCFR title number (1–50) for section lookup
sectionNoCFR section number (e.g. 1020.210) for section lookup

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
totalNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds material context beyond them: the returned fields (hierarchy, heading, text, last amended date, official URL), a 50,000-character text cap, the coverage boundary ('current CFR as published on ecfr.gov'), the cost ($0.003 per successful call via x402 USDC), and that failed calls are free. That pricing/auth and truncation disclosure is exactly what an agent needs before committing a paid call.

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?

Purpose and mode split are front-loaded in the first sentence, with return, coverage, sibling routing, and pricing following in a logical order. Slightly dense — the pricing sentence carries a lot of incidental detail — but no sentence is filler.

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 paid, read-only search/retrieve tool with an output schema and full annotation coverage, the definition closes every practical gap: what is returned, how text is capped, what corpus is covered, what it costs, and which sibling covers the adjacent need.

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 description coverage is 100%, so all five parameters (q, title, part, section, limit) are already documented with examples and constraints. The description only restates the title/part/section grouping used for lookup mode and adds no syntax or precedence rules (e.g., what happens if both q and title are supplied). 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?

Opens with a specific verb pair and resource: 'Searches the US eCFR by keyword or retrieves the current text of a specific section (title, part, section)' via the official API. The dual mode (keyword search vs. section lookup) is stated explicitly, and the sibling law_federal_register is named and characterized, so an agent can route correctly.

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 says when to reach for the alternative: 'law_federal_register when you need to search Federal Register documents by term or agency.' The implicit choice between keyword mode and section-lookup mode is derivable from the parameter names but is never spelled out as a rule, which keeps this short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources