Skip to main content
Glama

Federal Register Search Payment Quote

federal_register_search_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/federal-register/search (base $0.005; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?q=stablecoin (or agency=treasury-department; optional type=RULE|PRORULE|NOTICE|PRESDOCU, since=YYYY-MM-DD, limit=1-20). Federal Register search: up to 20 US rules, proposed rules, notices or presidential documents by keyword and/or agency, type and since-date. Returns document number, type, title, agencies, publication and effective dates, abstract and link. Public domain (1 CFR 2.6); not the official legal edition. No results, bad input or source down: not charged. USDC on Base only.

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": "federal_register_search_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotent, non-destructive), the description discloses the price ($0.005), the settlement constraint (USDC on Base only), and the billing-failure policy ("No results, bad input or source down: not charged") — all material facts annotations cannot convey. It stops short of describing quote expiry or any rate limits, which is the only remaining behavioral gap.

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?

Purpose and the never-pays disclaimer are front-loaded, and every clause carries information (price, payment protocol, parameters, return fields, licensing). It is dense and semicolon-chained, so the return-field list and licensing note compete for attention with the payment instructions, but little is genuinely wasted.

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?

There is no output schema, yet the description enumerates the return fields (document number, type, title, agencies, publication and effective dates, abstract, link) and the result cap of 20. Combined with the payment mechanics, licensing caveat, and failure-billing rule, an agent has everything needed to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty (0 parameters), so the description carries the whole burden, and it does: it documents q, agency, type (with the RULE|PRORULE|NOTICE|PRESDOCU enum), since=YYYY-MM-DD, and limit=1-20, including which are optional. That is meaning the schema cannot provide at all.

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 first sentence names a specific verb and resource — returns payment terms for the Federal Register search endpoint — and explicitly disclaims what it does not do ("never runs the check or pays"). That negative clause cleanly separates it from a hypothetical tool that actually executes the search, and the rest of the sentence describes the concrete resource the quote is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states the usage path directly: get the quote here, then "Pay the 402 over HTTP with x402 v2" via a GET with the listed query parameters. It also states the exclusion (this tool does not run the check or pay), which is exactly the routing information an agent needs against the *_quote siblings.

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.