Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Build macro event impact timeline

macro-intelligence_event-impact-timeline

Place supplied macro events on a timeline and attach nearby observations within 45 days. Causation is not claimed. Price $0.05 USDC. POST /api/v1/macro-intelligence/event-impact-timeline. 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_event-impact-timeline"
  }
}

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 carries the full burden and does disclose genuinely useful traits: no causal claim is made, the 45-day association window, the $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 without running. It stops short of describing the response shape, ordering, or what happens to events with no nearby observations.

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 operation, followed by the semantic caveat, then pricing and transport details. Nothing is padding, though the endpoint path restates what the tool name already conveys.

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, nested-input tool with no output schema and no annotations, the description is thin: it never explains what the timeline output looks like, how events are matched to observations, or how the many array inputs interact. It is adequate on billing and semantics but not on invocation.

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 and no per-field descriptions in the schema, so the description must compensate and largely does not. It only gestures at two inputs (events, observations) while csv/json/text/file, asOf, worldBank, and the debt/rates/tenors/releases/commodities/priceLevels arrays are entirely unexplained.

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?

"Place supplied macro events on a timeline and attach nearby observations within 45 days" gives a specific verb (place/attach), a specific resource (macro events, observations), and a concrete scope rule (45-day window). This clearly differentiates it from siblings like surprise-calculate or yield-curve-analyze, though it never names an alternative explicitly.

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?

The description implies you must supply events and observations, but there is no when-to-use / when-not-to-use guidance and no routing against the nine sibling analysis tools. An agent cannot tell from this text whether to reach for this tool or economic-indicator-release-track for a given question.

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