Wicked MCP server

macro_calendar

Read-onlyIdempotent

Retrieve upcoming US macro events like FOMC, CPI, and jobs reports with verified dates and rate-decision odds. Filter by event type or days ahead.

Instructions

[Trading Data API] Free, no signup required. Upcoming US macro events (FOMC rate decisions, CPI, jobs report) with verified Fed/BLS dates, days-until, and Kalshi rate-decision odds (cut/hold/hike) for FOMC meetings.

Example: /v1/macro-calendar

Use when you want upcoming US macro events (FOMC, CPI, jobs) with verified dates. Not for company earnings (use earnings_calendar).

Behavior: read-only and free; no key or payment needed.

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

Name	Required	Description	Default
`days`	No	Optional. Only events within the next N days.
`type`	No	Optional. Filter to FOMC, CPI, or NFP.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, and non-destructive; the description adds non-structured context that it is free, requires no key or signup, and that dates are verified against Fed/BLS sources. It does not mention rate limits, pagination, or the response envelope, so it falls short of a 5.

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?

Purpose, data contents, and the sibling exclusion are front-loaded and earned. The raw endpoint example (`/v1/macro-calendar`) and the repeated free/no-signup phrasing in both the header and the Behavior line are mild redundancy.

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 output schema, the description does the needed work by enumerating what comes back (dates, days-until, cut/hold/hike odds) and confirming no auth is needed. Pagination and response size limits are unstated, which is a minor gap for a calendar-style list 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?

Schema description coverage is 100%, so both parameters (days, type) are already documented in the schema. The description only indirectly clarifies that type values map to FOMC/CPI/jobs (NFP) and adds no format or boundary detail beyond that, so the baseline 3 applies.

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-and-resource: returns upcoming US macro events (FOMC, CPI, jobs report) with verified Fed/BLS dates, days-until, and Kalshi odds. It also explicitly distinguishes itself from the closest sibling by naming earnings_calendar as the wrong tool for company events.

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

Usage Guidelines5/5

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

Gives an explicit positive trigger ("Use when you want upcoming US macro events... with verified dates") and an explicit exclusion with the alternative to use instead ("Not for company earnings (use earnings_calendar)"). An agent has a complete routing rule.

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

Deploy Server