Skip to main content
Glama

BRAINIAC Regulatory Intelligence

Search US Federal Register

regulatory-intelligence_us-search
Read-onlyIdempotent

Search US Federal Register documents by keyword, agency, document type, and publication date using the official federalregister.gov API. Price $0.05 USDC. POST /api/v1/regulatory-intelligence/us/search. 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": {
      "query": "<query>"
    },
    "name": "regulatory-intelligence_us-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage, integer, from 1 to 9007199254740991. Required.
limitNolimit, integer, from 1 to 100. Required.
queryYesquery, string, length 1 to 200. Required.
agencyIdNoagencyId, integer, from 1 to 9007199254740991. Optional.
documentTypeNodocumentType, string, length 0 to 100. Optional.
publicationDateToNopublicationDateTo, string, date. Optional.
publicationDateFromNopublicationDateFrom, string, date. Optional.

Output Schema

NameRequiredDescriptionDefault
pageNopage. Number.
queryNoquery. String.
resultsNoresults. Array.
sourcesNosources. Array.
pageSizeNopageSize. Number.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
totalResultsNototalResults. Number.

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 declare readOnly/idempotent/non-destructive/openWorld, so the baseline is low; the description nonetheless adds two non-obvious facts: a $0.05 USDC price and that an unpaid call returns x402 payment terms instead of executing. That payment-gate behavior is exactly the kind of thing an agent cannot get from annotations. It stops short of describing rate limits, pagination caps (limit max 100, page ceiling), or result shape.

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?

Three short sentences, front-loaded with the action and resource, then cost, then endpoint, then the payment failure mode. No filler and nothing buried.

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?

An output schema exists and annotations are rich, so the description need not explain return values; it covers the two things structured fields cannot (price and the unpaid-call x402 handshake). Missing only secondary operational detail such as pagination guidance and how documentType/agencyId values are discovered via the sibling agencies tool.

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 the schema already names and constrains all seven parameters including date formats and bounds. The description's facet list merely mirrors query/agencyId/documentType/publicationDate ranges and adds no syntax, enum values for documentType, or agencyId lookup guidance, so baseline 3 applies.

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 ('Search US Federal Register documents') and enumerates the facets (keyword, agency, document type, publication date) plus the underlying official API. The 'US' qualifier and named source cleanly separate it from the UK siblings without needing to describe them.

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 by the verb 'Search' plus the facet list; there is no explicit statement of when to prefer this over us-details or us-agencies, and no exclusions or prerequisites beyond the payment note. An agent can infer this is the entry point for document retrieval, but the routing is left to inference.

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