Skip to main content
Glama

Market Intelligence API (core)

Macro calendar

macro.calendar
Read-onlyIdempotent

Next market-moving events ($0.10) in UTC with importance, from official calendars: US CPI, jobs report, PCE, GDP, PPI, JOLTS (BLS, BEA), FOMC and ECB rate decisions. Check before opening a position.

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.calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to cover (look-back; days ahead for calendars)
regionNoRegion: all, us or euall
importanceNoMinimum importance of the events to includemedium

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context beyond those fields: events are returned in UTC, sourced from official calendars (BLS, BEA), and cost $0.10 — a genuine cost/behavior disclosure. It omits anything about result size or ordering when the requested window has many events.

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?

Two short sentences, front-loaded with what the tool returns and its unit/timezone. The inline price tag is slightly awkward mid-sentence but is not redundant, and no sentence is wasted.

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?

No output schema, so the description does what it can by specifying the timezone, the importance attribute per event, and the source of truth. It does not describe the returned event object's shape (e.g., timestamp, name, country), which would be needed for full completeness on a data-returning tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already explains days, region, and importance including their enums and defaults. The description only echoes 'importance' and does not clarify the look-back semantics of 'days' or the region scope, so it does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb/resource combination: 'Next market-moving events ... with importance, from official calendars', followed by concrete event types (CPI, jobs report, FOMC) that make the resource unambiguous. It is clearly a macro events calendar, distinguishable from siblings like macro.fed_odds or news.symbol.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Check before opening a position' gives an explicit trigger context for when to call the tool. It stops short of naming alternatives or exclusions (e.g., when to prefer macro.fed_odds for odds rather than event dates), so it falls short of a 5.

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