Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Analyze commodity price transmission

macro-intelligence_commodity-price-transmission-analyze

Compare supplied commodity price changes with inflation observation changes. Causation is not claimed. Price $0.05 USDC. POST /api/v1/macro-intelligence/commodity-price-transmission-analyze. 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_commodity-price-transmission-analyze"
  }
}

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/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the $0.05 USDC cost, POST endpoint, and that unpaid calls return 402 without running, plus a causation disclaimer. However, it omits whether the operation is read-only, how multiple input formats interact, and what the result contains.

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 four concise sentences with the purpose front-loaded and no wasted wording. The payment, endpoint, and disclaimer details are tightly packed and relevant to invocation.

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 complex tool with 15 parameters, nested objects, no annotations, and no output schema, the description is far too thin. It provides operational cost and payment context but not enough input-format guidance or output expectations for an agent to invoke it confidently.

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 parameters, and the description only alludes to commodity prices and inflation observations. It does not explain the many other parameters such as csv, file, json, text, worldBank, priceLevels, debt, rates, or how to choose among input formats.

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 states a specific verb and resource: comparing commodity price changes with inflation observation changes. It does not name sibling alternatives or explicitly distinguish itself from tools like inflation-series-compare, so it falls 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?

It does not explain when to use this tool versus related siblings, nor does it give prerequisites or exclusions beyond the payment requirement. The causation disclaimer is a caveat, not 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