Skip to main content
Glama

BRAINIAC Bills & eCFR Section Lookup

Look up an eCFR section (titles 16, 17, 29)

legislative-intelligence_ecfr-section-lookup
Read-onlyIdempotent

Return the text of one CFR section from the vendored eCFR snapshot of titles 16, 17 and 29. Price $0.03 USDC. POST /api/v1/legislative-intelligence/ecfr-section-lookup. An unpaid call returns the x402 payment terms and does not run.

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": {
      "title": "<title>",
      "section": "<section>"
    },
    "name": "legislative-intelligence_ecfr-section-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYestitle, value. Required.
formatNoformat, string, one of text, xml. Required.text
sectionYessection, string. Required.

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
textNotext. String.
foundNofound. Boolean.
titleNotitle. Number.
ecfrUrlNoecfrUrl. String.
headingNoheading. String.
sectionNosection. String.
sourcesNosources. Array.
citationNocitation. String.
reservedNoreserved. Boolean.
hierarchyNohierarchy. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description adds real context: a $0.03 USDC price, an x402 payment gate, and the fact that an unpaid call returns payment terms instead of executing. It stops short of noting snapshot staleness or rate limits, which matters for a 'vendored' data source.

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?

Four short sentences with the purpose front-loaded, followed by cost, endpoint, and failure behavior. The raw endpoint path is marginal filler for an agent, but nothing is redundant or padded.

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?

An output schema exists, so return values need not be explained, and the description covers the remaining agent-critical facts: scope of titles, cost, payment gating, and behavior on unpaid calls. For a single-record read tool this is sufficient to call correctly.

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 three parameters (title, section, format) are already documented with an enum and a regex pattern. The description restates the allowed title set but adds no syntax or format guidance beyond 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?

States a specific verb and resource — 'Return the text of one CFR section' — and bounds it to the vendored eCFR snapshot of titles 16, 17 and 29. The resource (CFR section text) is clearly distinct from the sibling bill-status tools, so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description makes clear this is a single-section lookup against a fixed snapshot, but it never says when to prefer it over another source or when-not to call it (e.g. titles outside 16/17/29). No alternatives are named.

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