Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Federal Register search: US rules and notices

gov_federal_register
Read-only

Search the US Federal Register: final rules, proposed rules, notices and presidential documents, newest first, with title, type, agencies, abstract, publication date, comment deadline, effective date and links. Filter by type and agency; sort=relevance puts the documents that are most about the words first. From the Federal Register API (US government work). Use to track new regulations or open comment periods on a topic. Example: q=artificial intelligence. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "q": "<q>"
    },
    "name": "gov_federal_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, e.g. artificial intelligence
sortNonewest (default) or relevance
typeNorule, proposed_rule, notice or presidential (default all)
limitNoDocuments to return, 1-20 (default 10)
agencyNoAgency slug, e.g. securities-and-exchange-commission (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/destructive/openWorld annotations, it discloses the cost model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), that each call is billable so repeats are not free, and that the operation only reads. The pricing/repeat-charge note is exactly the kind of operational fact annotations cannot convey and is consistent with idempotentHint=false.

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?

Front-loaded with purpose, then filters, then provenance, then usage, then pricing — a sensible order. It is dense but slightly overstuffed; the licensing aside "(US government work)" and the trailing restatement that calls are charged add minor redundancy.

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?

With no output schema, the description compensates by listing the fields returned, the ordering, the filter dimensions, and the billing behavior. Nothing an agent needs in order to call this correctly or decide whether to repeat a call is missing.

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 coverage is 100%, so the baseline is 3, but the description goes further: it maps the document categories to the type filter, explains what relevance sorting actually means ("documents that are most about the words"), and states the newest-first default. Agency slug handling is left to the schema, which already provides an example.

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 names a specific verb and resource ("Search the US Federal Register") and enumerates the covered document classes (final rules, proposed rules, notices, presidential documents) plus the returned fields and default ordering. An agent knows exactly what corpus is being queried and what it gets back, 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 Guidelines4/5

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

It gives a concrete use case ("track new regulations or open comment periods on a topic") plus a worked example (q=artificial intelligence) and explains when to prefer sort=relevance over the default newest-first. It does not name an alternative tool to use instead for non-regulatory search, but no sibling in the list is a plausible substitute, so this is clear context without exclusions.

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.