Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Compare currency purchasing power

macro-intelligence_currency-purchasing-power-compare

Compare supplied price indexes adjusted by FX-per-USD values. Missing FX or price indexes are not invented. Price $0.05 USDC. POST /api/v1/macro-intelligence/currency-purchasing-power-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_currency-purchasing-power-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.1/5.0
Behavior3/5

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

With zero annotations the description carries the full behavioral burden, and it does disclose several useful traits: missing FX or price indexes are not fabricated, the call costs $0.05 USDC, it POSTs to a stated endpoint, and unpaid calls return 402 without running. It omits what the comparison returns and how the many optional input collections affect the result.

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, front-loaded sentences with no filler: capability first, then data-handling guarantee, then price and endpoint, then failure behavior. Telegraphic but every sentence carries information.

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?

Placeholder.

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?

Fifteen parameters with 0% schema description coverage, so the description must compensate and largely does not. It only implicitly identifies priceLevels (price index plus fxPerUsd) as the operative input and leaves csv, json, text, file, debt, rates, events, series, tenors, releases, worldBank, commodities and observations entirely unexplained, including whether they are alternative formats or supplementary context.

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 price indexes adjusted by FX-per-USD values. That is distinguishable from sibling operations such as yield-curve analysis or inflation-series comparison, though the description never names an alternative to differentiate against.

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 or when-not-to-use guidance and no mention of the sibling tools. The only conditional statement is about missing data (not invented) and payment failure (402), which is operational rather than usage 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