Skip to main content
Glama

BRAINIAC Regulatory Intelligence

Get US Federal Register agencies

regulatory-intelligence_us-agencies
Read-onlyIdempotent

Retrieve list of US Federal Register agencies with their IDs and metadata from the official federalregister.gov API. Price $0.02 USDC. POST /api/v1/regulatory-intelligence/us/agencies. An unpaid call returns the x402 payment terms and does not run.

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": "regulatory-intelligence_us-agencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage, integer, from 1 to 9007199254740991. Required.
limitNolimit, integer, from 1 to 200. Required.
queryNoquery, string, length 0 to 200. Optional.

Output Schema

NameRequiredDescriptionDefault
pageNopage. Number.
sourceNosource. Object.
agenciesNoagencies. Array.
pageSizeNopageSize. Number.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
totalResultsNototalResults. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable operational context not present in annotations: a $0.02 USDC price and the fact that an unpaid call returns x402 payment terms without running the request.

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 front-loaded and compact: purpose first, then price, then endpoint and unpaid-call behavior. It is efficient, though the endpoint line is slightly mechanical and could be merged with the payment note.

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?

The tool has an output schema, full annotation coverage, and fully described parameters, so the description does not need to explain return values. It covers purpose, source, cost, and unpaid-call behavior; the main completeness gap is missing guidance on when to select this tool versus its siblings.

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% for the three parameters (page, limit, query), so the schema already carries their meaning. The description adds no parameter-specific semantics beyond what is in the structured schema.

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: "Retrieve list of US Federal Register agencies with their IDs and metadata" from the official federalregister.gov API. It does not explicitly distinguish this list endpoint from sibling search/detail tools, 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 Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer that this lists agencies, but the definition does not route it against siblings such as regulatory-intelligence_us-search or regulatory-intelligence_us-details.

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