Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Economic Calendar

get_economic_calendar
Read-only

Retrieve scheduled macroeconomic events such as CPI, FOMC, jobs reports, and GDP between two dates, with an optional country filter (defaults to US).

Instructions

Get scheduled macro/economic events (CPI, FOMC, jobs reports, GDP, etc.) between two dates. Optionally filter to a single country (ISO-3166 alpha-2, e.g. "US"). Defaults to US when omitted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_economic_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd date inclusive (YYYY-MM-DD)
fromYesStart date inclusive (YYYY-MM-DD)
countryNoOptional ISO-3166 alpha-2 country code (e.g. "US", "GB", "JP")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — country defaults to US when omitted — but says nothing about pagination, maximum range, or whether non-US coverage is complete. An output schema exists, so return-shape detail is not required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero waste: action and scope first, the optional filter second, the defaulting rule last. Nothing is buried and no sentence is redundant with the schema.

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 annotations covering safety, a full input schema, and an output schema, the description supplies what structured fields cannot: event-type examples and the US default. The remaining gap is routing guidance against the many sibling calendar tools, which matters given how many calendars exist in this server.

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 baseline would be 3, but the description adds meaning the schema lacks: that `country` defaults to 'US' when omitted and that it filters to a single country, plus format examples for the event types returned. That defaulting behavior is a genuine semantic addition beyond the raw schema.

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 resource ('Get scheduled macro/economic events') and enumerates concrete event types (CPI, FOMC, jobs reports, GDP) plus the date-range scope. It implicitly differs from calendar siblings like get_earnings_calendar or get_filing_calendar by being macro-level, but it never names or excludes those siblings explicitly.

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 scope ('scheduled macro/economic events between two dates') implies when this tool is appropriate, but there is no explicit when-to-use versus get_earnings_calendar, get_filing_calendar, get_legislative_calendar, or get_policy_events. It also gives no guidance on date-range limits or expected result volume.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools