Skip to main content
Glama

Economic calendar

get_economic_calendar

Upcoming economic news events (NFP, CPI, central banks…) with their impact level (High/Medium/Low), time (UTC), forecast and previous value. Filter by symbol (e.g. XAU_USD shows USD events) or currency, and by minimum impact. Use it to warn the user before high-impact news that affects an open position or a plan, and to time entries. Covers the current week ahead (and the recently accumulated past). Read-only; source: ForexFactory calendar feed.

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": "get_economic_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays ahead to cover, 1-14 (default 7).
impactNoMinimum impact to include (default: medium).
symbolNoTraderWAI symbol (e.g. EUR_USD, XAU_USD): shows the events of its currencies.
currencyNoOne or several currencies, comma-separated (e.g. "USD,EUR"). Ignored if symbol is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/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 reasonably well: it declares the tool read-only, names the data source (ForexFactory feed), states the coverage window, and notes that the historical portion is only 'recently accumulated'. It does not discuss freshness/latency or refresh cadence of the feed, which would matter for news-timing decisions.

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?

Three dense sentences, front-loaded with what the tool returns before moving to filtering and then use cases. Every sentence carries information, though the parenthetical examples and the trailing provenance clause could be tightened slightly.

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?

With no annotations and no output schema, the description compensates by describing the returned fields, timezone, coverage window, defaults, and read-only nature. The only soft gap is the tension between 'covers the current week ahead' and a days parameter allowing up to 14, which is left unexplained.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline, but the description adds real meaning beyond the schema: it explains that a symbol like XAU_USD expands to its underlying currencies' events, and it links the minimum-impact filter to the impact levels returned. The symbol/currency precedence is already in the schema, so it is not double-counted.

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?

The description names a specific resource (upcoming economic news events such as NFP, CPI, central banks) and enumerates the returned fields (impact level, UTC time, forecast, previous). It also states the scope explicitly — current week ahead plus recently accumulated past — so an agent can tell immediately what this tool does and does not return.

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?

It gives concrete usage conditions: warn the user before high-impact news affecting an open position or plan, and time entries. It also describes filtering options (symbol vs currency vs minimum impact) so the agent knows how to narrow results, though it names no alternative tool or explicit when-not condition.

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