Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Compare central bank rates

macro-intelligence_central-bank-rate-compare

Compare supplied policy rates across countries and banks. Missing previous rates leave change blank rather than inventing values. Price $0.04 USDC. POST /api/v1/macro-intelligence/central-bank-rate-compare. Unpaid calls return 402 and do not run.

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-intelligence_central-bank-rate-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
debtNo
fileNo
jsonNo
textNo
ratesNo
eventsNo
seriesNo
tenorsNo
releasesNo
worldBankNo
commoditiesNo
priceLevelsNo
observationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does disclose meaningful behavior: the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 and never execute. It also states an important data-integrity policy — missing previous rates yield blank change values rather than fabricated ones. What it does not cover is the shape of the comparison result, which matters since there is no output schema.

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?

Four short sentences, front-loaded with purpose, followed by the data-integrity caveat, price, endpoint, and payment failure mode. Nothing is padded, though the endpoint path is marginally redundant with the tool name and could have been spent on input guidance instead.

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

Completeness2/5

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

This is a high-complexity tool: 15 parameters, nested objects, no annotations, and no output schema. The description covers billing and payment failure well but leaves both the input contract and the returned comparison structure undocumented, which is a substantial gap for an agent trying to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% across 15 top-level parameters, several with nested objects, so the description must compensate and largely fails to. It hints at the 'rates' array and the 'previousRate' field, but says nothing about the many alternative input channels (csv, json, text, file, worldBank) or how they interact. An agent must reverse-engineer the input contract entirely from the raw 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 first sentence gives a specific verb and resource: 'Compare supplied policy rates across countries and banks.' The word 'supplied' usefully signals that input data drives the comparison rather than a server-side fetch, distinguishing it from siblings like yield-curve-analyze. It stops short of naming an alternative tool or stating how it differs from the other comparison tools in the family.

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 rather than stated: the agent learns the tool compares rates it supplies and that missing 'previous rates' simply yield blank change fields. There is no explicit when-to-use/when-not-to-use guidance and no reference to sibling tools such as inflation-series-compare or yield-curve-analyze, so selection between them must be inferred from the resource name alone.

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