Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

earnings_calendar

Read-onlyIdempotent

Fetches upcoming US equity earnings dates, before/after-market timing, analyst EPS estimates, and market cap, so you can schedule trades around earnings events.

Instructions

[Trading Data API] US equity earnings announcement calendar: report date, before/after-market timing, analyst EPS estimate + count, market cap, and prior-year actual EPS. Sourced live from Nasdaq's public calendar.

Example: /v1/earnings-calendar?date=2026-07-14&days=3

Use when you want upcoming US earnings dates, timing and analyst estimates. Not for macro events (use macro_calendar) or filed reports (use filings_search).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. Start date YYYY-MM-DD (default: today).
daysNoOptional. Days to scan forward from date (default 1, max 7).
symbolNoOptional. Filter to one ticker within the scanned range.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavioral context: the Nasdaq live source, x402 USDC-on-Base pricing, free-with-API-key path, and — critically — that an HTTP 402 carries a decoded price quote rather than being a failure. That last detail prevents an agent from misreading a paywall response as an error.

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?

Front-loaded with the resource and field list, then example, then when-to-use/alternatives, then behavior. Every sentence carries distinct information; nothing restates the schema or annotations redundantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description compensates by enumerating the returned fields, so an agent knows what it gets back. Combined with payment and error-path disclosure, nothing needed to call this correctly is missing.

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 the baseline is 3. The description adds value beyond the schema by threading date and days together in a concrete example (`?date=2026-07-14&days=3`), clarifying that days is a forward scan window from date. It stops short of explaining how symbol interacts with the range, which the schema only lightly covers.

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 ('US equity earnings announcement calendar') and enumerates the exact fields returned (report date, BMO/AMC timing, EPS estimate + count, market cap, prior-year EPS). Explicitly distinguishes itself from macro_calendar and filings_search by name.

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?

'Use when you want upcoming US earnings dates, timing and analyst estimates' gives the positive condition, and 'Not for macro events (use macro_calendar) or filed reports (use filings_search)' names both alternatives and the conditions that select them.

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