Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Compare inflation series

macro-intelligence_inflation-series-compare

Compare supplied CPI or inflation observations by country using the latest and previous points only. Price $0.04 USDC. POST /api/v1/macro-intelligence/inflation-series-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_inflation-series-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

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry real burden, and it discloses two useful behaviors: the $0.04 USDC cost and that unpaid calls return 402 without executing. It omits what an agent would still want to know for a mutation-free compute call — whether input is validated, which of the 15 input forms is preferred, and what happens with insufficient or single-point data.

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 with the analytical scope front-loaded and no filler. The pricing and endpoint sentences are dense but each carries distinct information; nothing is padded.

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?

For a 15-parameter tool with nested objects, no annotations, and no output schema, the description is thin — it explains what is compared but not how to supply data across the overlapping input channels. An agent cannot decide between observations, csv, json, text, or file from this text alone.

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 coverage is 0% across 15 parameters, and the description only hints at the observations array via 'CPI or inflation observations' and 'by country'. It says nothing about asOf, csv, json, text, or whether the many unrelated collections (debt, rates, tenors, releases, commodities, priceLevels, worldBank) are ignored, accepted, or required.

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 ('compare supplied CPI or inflation observations by country') plus the analytical rule ('latest and previous points only'), which tells an agent what the output framing is. It does not explicitly contrast itself with siblings such as surprise-calculate or economic-indicator-release-track, so it stops short of a 5.

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?

There is no when-to-use guidance: no statement of what data must already be in hand, no exclusions, and no pointer to an alternative when the agent wants a full time series rather than a two-point comparison. The 'supplied' wording weakly implies a data-in tool but leaves the agent to infer the rest.

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