Skip to main content
Glama

Agent Exchange store

signals_federal_register

$0.002 via x402: US Federal Register documents (rules, proposed rules, notices, presidential documents) newest first, by search term and optional type and agency: title, type, agencies, publication date, abstract, document number, links. Pay 0.002 USDC through https://store.agentexchange.work/gw/signals/federal-register?q=artificial+intelligence Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
qYesq
typeNoRULE, PRORULE, NOTICE or PRESDOCU
limitNo1..50, default 20
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real context: the exact $0.002 cost, the x402/USDC payment flow through the Agent Exchange gateway settled by Coinbase, and the fields returned. It omits rate limits and error/refund behavior, but the payment and output profile is unusually well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one dense sentence that front-loads price rather than purpose, repeats the cost twice ($0.002 and 0.002 USDC), and embeds a full gateway URL. Functional but not cleanly structured or optimally front-loaded.

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?

For a paid endpoint with no output schema, the description supplies the return-field list, the payment requirement, and the settlement mechanism, so an agent knows what it gets and what it must pay. Missing detail on pagination and the price-return behavior (covered only in the schema) keeps it short of a 5.

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 documents q, type, limit, and x_payment, making 3 the baseline. The description adds only a field list and mentions 'optional type and agency', yet no agency parameter exists in the schema, which could mislead an agent into passing an unsupported filter.

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?

States a specific verb and resource: retrieves US Federal Register documents (rules, proposed rules, notices, presidential documents) newest-first, filtered by search term with optional type. Clear enough that an agent distinguishes it from siblings like signals_hn or signals_quakes, though no sibling is named explicitly.

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?

Implies usage via 'by search term and optional type and agency' and the required q parameter, but never states when to prefer this over alternatives or when it is inappropriate. No explicit exclusions or routing guidance.

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