Genexxis paid agent tools (x402)

macro_policy_rates

Central bank policy rates for 39 economies from BIS official data: current rate, date of last change and size in bp, year-ago rate, central bank name. Filter by ISO country codes (US, XM for euro area, MA, ZA...). Price: $0.005 USDC per call, paid with x402 on Base.

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

Input Schema

Name	Required	Description	Default
`country`	No	Comma-separated ISO2 codes; XM = euro area. Omit for all 39.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and usefully discloses the paid x402/Base pricing model, the official BIS data source, and the returned fields. It does not cover error behavior or rate limits, but for a simple read-only data endpoint the key behavioral context is present.

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?

The description is compact and front-loaded: it states the dataset and coverage first, then filtering, then pricing. Every sentence adds useful information with no wasted prose.

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 one-parameter retrieval tool with no output schema and no annotations, the description is largely complete: it names the returned fields, data source, filtering behavior, and payment requirement. It could be stronger on sibling selection and output shape, but no critical information is missing for invocation.

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 single optional country parameter is already fully documented in the schema. The description repeats the ISO2 filtering examples and XM euro-area meaning but adds no material semantics beyond the schema.

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 description names a specific resource (central bank policy rates) and specifies the source (BIS), coverage (39 economies), and returned fields. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as macro_fx or yields_rate.

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

Usage Guidelines2/5

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

It explains how to filter by ISO country codes and that omitting the parameter returns all 39, but it gives no guidance on when to use this tool versus related alternatives like macro_fx or yields_rate. The usage context is only implied by the purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?