Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Calculate macro surprises

macro-intelligence_surprise-calculate

Calculate actual-minus-consensus surprises from supplied releases and optional z-scores against the sample stdev. Price $0.05 USDC. POST /api/v1/macro-intelligence/surprise-calculate. 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_surprise-calculate"
  }
}

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
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose valuable operational traits: the $0.05 USDC price, the POST path, and that unpaid calls return 402 without running. But it never says whether the computation is pure/non-destructive, what the response contains, or how missing consensus values are handled across the 15 input families.

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 the computation, then cost, endpoint, and payment failure mode. Every sentence carries information and nothing is padded, though the endpoint string is largely redundant with the tool name.

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 complex tool: 15 top-level parameters including arrays of nested objects, no output schema, and no annotations. The description addresses only a fraction of that surface and says nothing about which inputs are actually required to produce a surprise value, so an agent cannot confidently construct a call.

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, many nested, so the description must compensate heavily and does not. It mentions only 'releases' and a 'z-scores' option, and no z-score parameter appears in the schema, leaving the reader unsure how that option is expressed. The other 13 parameters (csv, file, debt, rates, tenors, worldBank, etc.) get no explanation of relevance to the surprise calculation.

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 computation ('calculate actual-minus-consensus surprises') plus the input source ('supplied releases') and the optional normalization ('z-scores against the sample stdev'). That distinguishes it from siblings like economic-indicator-release-track or inflation-series-compare, which name different verbs and resources. It stops short of 5 because the scope of the output is never stated.

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?

The phrase 'from supplied releases' implies this tool operates on caller-provided data rather than fetching, which is useful context, but there is no explicit when-to-use or when-not-to-use guidance against the nine sibling analytics tools. An agent must infer that this is the post-processing step after gathering releases elsewhere.

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