Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Economic calendar

economic_calendar_list
Read-only

List macroeconomic events like CPI and payrolls over a date range, with actual, previous, and consensus figures. Filter by country, impact, or agency.

Instructions

List scheduled and released macroeconomic events (e.g. CPI, non-farm payrolls, rate decisions) over a date range, each with its actual, previous, and consensus figures. Filter by country, impact level, issuing agency, or a specific recurring event_id. Defaults to the US and roughly the next 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoUpper bound, YYYY-MM-DD or RFC3339. Default: from + 30 days.
fromNoLower bound, YYYY-MM-DD or RFC3339. Default: now.
limitNo1-500. Default 100.
agencyNoIssuing agency: BLS, BEA, Census, Fed, DOL, EIA.
impactNoImpact level: low, medium, high.
countryNoTwo-letter country code. Default: US.
event_idNoFilter to a single recurring event, e.g. us_cpi.
Behavior4/5

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

Annotations indicate read-only; description adds that it lists both scheduled and released events with figures. Does not contradict annotations and provides useful behavioral context beyond them.

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?

Single, well-structured sentence that front-loads the core action and then details defaults and filters with zero wasted words.

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?

Covers return fields (actual, previous, consensus), defaults, and common filters. Lacks mention of pagination or response format, but sufficient for a list tool with a limit parameter.

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 has 100% coverage, but description adds meaningful context like defaults, filtering purpose, and concrete example (event_id: us_cpi), enhancing understanding beyond schema alone.

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 states it lists scheduled and released macroeconomic events over a date range with specific figures (actual, previous, consensus), clearly distinguishing it from sibling tools like stocks_earnings or markets_calendar.

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?

Provides clear context on defaults (US, next 30 days) and filtering options (country, impact, agency, event_id), but does not explicitly state when not to use or compare with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiftingIO/siftingio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server