Skip to main content
Glama
Sign In

X3 Compliance

by io.github.x3allamerican
OverviewDiscussionsAdmin

Read a federal regulation (eCFR)

cfr_lookup
Read-onlyIdempotent

Get the current (or dated) text of a Code of Federal Regulations citation such as "49 CFR 395.3(a)(2)" or "29 CFR 1910.147(c)(4)" from the official eCFR, paragraph by paragraph with a citation and link for each.

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": {
      "citation": "<citation>"
    },
    "name": "cfr_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD to read the rule as of that date (optional)
citationYesA section citation with a title, e.g. 49 CFR 192.605(b)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds meaningful behavior beyond that: the source is the official eCFR and results come back paragraph by paragraph with a citation and link for each, which tells the agent what the response looks like. It does not cover failure behavior for malformed or nonexistent citations.

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?

A single sentence with no filler, front-loaded on the action and source, with examples appended for grounding. Nothing is redundant.

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?

There is no output schema, and the description compensates by describing the return shape (paragraph-by-paragraph with per-paragraph citations and links) and the data source. What it lacks is edge-case behavior, such as what happens for an invalid citation or a section that has been removed.

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 coverage is 100%, so both parameters are already documented in the schema. The description reinforces the citation format with realistic examples and implies the date parameter selects a historical version, but adds no syntax or constraint detail beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Get the current (or dated) text of a Code of Federal Regulations citation' from the official eCFR, with concrete citation examples. It does not explicitly distinguish itself from the sibling tools cfr_changes or cfr_search, so it stops short of a 5.

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: you call it when you have a specific citation and want its text. There is no explicit when-to-use or when-not guidance, and no mention of when to prefer cfr_search (discovery) or cfr_changes (diffs) instead.

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

All X3 Compliance 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