Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Track economic indicator releases

macro-intelligence_economic-indicator-release-track

Track supplied indicator release dates with actual, consensus, and previous values when present. Price $0.04 USDC. POST /api/v1/macro-intelligence/economic-indicator-release-track. 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_economic-indicator-release-track"
  }
}

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 behavioral burden. It usefully discloses pricing ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 and do not run, which is meaningful operational context. However, it does not clarify persistence, idempotency, output shape, or side effects for a complex supplied-data operation.

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?

The description is three sentences and front-loads the core purpose before operational details. Every sentence has a role, including price and payment failure behavior, with little wasted wording.

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 too thin. It explains the high-level purpose and payment behavior but does not give an agent enough information to understand which input families to supply or how to invoke the tool correctly.

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?

The schema has 15 parameters with 0% description coverage, including many nested arrays such as debt, rates, events, series, tenors, releases, worldBank, commodities, priceLevels, and observations. The description only hints at the releases array by mentioning actual, consensus, and previous values when present, leaving most parameter semantics undocumented.

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: 'Track supplied indicator release dates with actual, consensus, and previous values when present.' This is clear enough for an agent to understand the tool's core function. It does not distinguish itself from siblings such as surprise-calculate or event-impact-timeline, 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?

The definition gives no explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. The purpose implies usage, but there is no routing context for choosing among the many macro-intelligence siblings.

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