Skip to main content
Glama

BRAINIAC Regulatory Intelligence

Get US Federal Register document details

regulatory-intelligence_us-details
Read-onlyIdempotent

Retrieve US Federal Register document details and effective dates from the official federalregister.gov API. Price $0.03 USDC. POST /api/v1/regulatory-intelligence/us/details. 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": {
      "documentNumber": "<documentNumber>"
    },
    "name": "regulatory-intelligence_us-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNumberYesdocumentNumber, string, length 1 to 50. Required.

Output Schema

NameRequiredDescriptionDefault
foundNofound. Boolean.
sourceNosource. Object.
documentNodocument. Null.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
documentNumberNodocumentNumber. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavior, but the description adds genuinely new context: the $0.03 USDC price, the concrete endpoint, and the important detail that an unpaid call returns x402 payment terms without executing. That payment-gating behavior is invisible in the annotations and is exactly what an agent needs to avoid misreading an unpaid response as a result.

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?

Three short sentences, front-loaded with the purpose and followed by cost and payment behavior; nothing is padded. The literal endpoint path is arguably redundant given the tool name, but it remains useful for an agent reasoning about the API surface.

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?

Return values need not be described since an output schema exists, and the annotations plus description cover safety, cost, and payment gating for a simple single-parameter read. The only gap is the absence of guidance on failure modes such as an unknown or malformed documentNumber.

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?

With one parameter at 100% schema description coverage, the schema already documents documentNumber's type, length bounds, and required status. The description adds no format guidance (e.g., sample document number shape) beyond what the schema provides, so the 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 ("Retrieve US Federal Register document details and effective dates") plus the authoritative source (federalregister.gov API), which cleanly separates it from the UK-details, us-search, and us-agencies siblings. An agent knows exactly what this returns 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 implied by the required documentNumber parameter — you fetch details for a document you already have an identifier for. However, it never says to use us-search first to obtain a documentNumber, nor does it state what happens when a document is not found. No explicit alternatives or exclusions 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