Skip to main content
Glama

Central Bank Policy Rates Payment Quote

policy_rates_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/rates/policy (base $0.005; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET with no parameters (all 7 banks), or ?banks=fed,ecb,boe; add allow_partial=true to accept a charged partial answer. Current policy rates from 7 central banks in one call: Fed target range, ECB, BoE, BoC, RBA, RBNZ and Riksbank, each with its date and source link. Values are taken from each bank's own website, where they are published free of charge; the fee covers the multi-bank lookup, and no restrictions are added. Not affiliated with or endorsed by any central bank. Information only, not advice. Charged only when every requested bank is delivered, unless allow_partial=true. USDC on Base or Polygon. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (nati

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes well beyond that with charging semantics an agent cannot infer: charged only when every requested bank is delivered unless allow_partial=true, errors uncharged on Base but potentially charged on Solana and XRP Ledger, and an explicit no-affiliation/no-advice disclaimer. The final sentence is truncated mid-word ('On Polygon (nati'), leaving one chain's charging rule incomplete.

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

Conciseness2/5

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

Purpose is front-loaded, but the body is a dense run-on mixing four unrelated topics: payment terms, HTTP invocation, the underlying dataset's contents and licensing, and per-chain charging exceptions. 'USDC on Base or Polygon' is repeated, and the text is cut off mid-sentence, so the reader cannot tell whether content was lost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description carries the burden of explaining what a 'quote' actually returns, and it only partly does so — a base price of $0.005 and payment rails are given, but the shape of the response (402 challenge, price object) is never described. The truncated tail leaves the Polygon charging rule unresolved. Enough to attempt a call, not enough to predict the result confidently.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description still adds meaning by explaining the downstream query options (banks list, allow_partial) that determine what the quoted price covers, even though those are not schema properties. The risk is mild confusion between tool inputs and endpoint parameters, but nothing is misleading.

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 opening sentence states a specific verb and object — returns payment terms for a named rates endpoint — and explicitly disclaims execution ('this tool never runs the check or pays'), which distinguishes it from a data-fetch tool. However, most of the remaining text describes the underlying API's payload (Fed range, ECB, BoE, etc.), which blurs whether the tool returns rates or a price quote. It never names a sibling like money_market_rates or treasury_yield_curve to sharpen the boundary.

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?

It gives concrete invocation mechanics for the paid endpoint (GET with no parameters for all 7 banks, or ?banks=fed,ecb,boe, plus allow_partial=true), which is real usage guidance. But it never says when an agent should call this quote tool rather than a sibling rates tool, nor what to do with the returned terms next. Guidance is implied through the payment flow rather than stated as when/when-not.

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.