QuantGeeks GEX

Earnings and macro calendar

quantgeeks_get_earnings_calendar

Read-onlyIdempotent

Without signing in: the macro and earnings schedule for a date range (event, date and time in US Eastern, and the session for earnings), without estimates, results or moves. Signed in with a free QuantGeeks account: the same. With a QuantGeeks plan: the same plus the estimate and actual, the surprise, the straddle-implied move and the actual move. US macro releases, company earnings and SEC filings for a date range, chronological, at most 40 rows (detail 'all' lifts the cap), times in US Eastern (earnings by session: before open, during, after close). Default: today through the end of next week; at most 21 days. Filter with kind (macro, earnings, filings) and symbols (earnings and filings for those tickers). A plan adds EPS and revenue estimate against actual, the surprise, the straddle-implied move before the print, the actual move, and who the straddle paid. The answer carries an attribution (a data credit, CC BY-SA 4.0): pass it along when you share the data. For forward option positioning into a print use quantgeeks_get_expiration_map.

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

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD. Default: the end of next week; the range is at most 21 days.
`from`	No	First day, YYYY-MM-DD (US Eastern). Default: today.
`kind`	No	'all' (default), 'macro', 'earnings' or 'filings'.
`detail`	No	'summary' (default): the first 40 rows; 'all': every row in the range.
`symbols`	No	Only earnings and filings for these tickers, e.g. ["NVDA","AAPL"].

Output Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`kind`	Yes
`note`	No
`as_of`	Yes
`count`	Yes
`access`	Yes
`events`	Yes
`notice`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`preview`	Yes
`symbols`	No
`pro_plan`	No
`plan_note`	No
`times_are`	Yes
`truncated`	No
`attribution`	No
`account_note`	No
`truncated_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the read-only/idempotent annotations: a hard cap of 40 rows that only detail='all' lifts, a default window of today through next week with a 21-day maximum, US Eastern times, and earnings bucketed by session. It also discloses the CC BY-SA 4.0 attribution obligation and tells the agent to pass the credit along — a real behavioral constraint that structured fields do not carry.

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?

Content is front-loaded enough that an agent learns scope, caps and timezone quickly. However, the tier benefits are enumerated twice ('With a QuantGeeks plan: the same plus...' then 'A plan adds EPS and revenue estimate against actual...'), which is avoidable repetition in an otherwise dense definition.

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?

For a five-parameter, read-only calendar with an output schema and full annotations, nothing essential is missing: scope, filters, caps, default range, timezone, ordering, tier-gated fields, attribution duty and the alternative tool are all covered.

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 the schema already documents to, from, kind, detail and symbols, including the 25-ticker limit and enum values; the baseline is therefore 3. The description largely restates those same defaults and filters, adding only marginal meaning (e.g. symbols applies only to earnings and filings).

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: 'US macro releases, company earnings and SEC filings for a date range, chronological' with times in US Eastern. The tiering (anonymous/ free account / plan) makes clear exactly which fields are returned, which no sibling could be confused with.

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?

Gives an explicit routing rule to a named alternative: 'For forward option positioning into a print use quantgeeks_get_expiration_map.' This is a real when-to-use-elsewhere signal. It stops short of stating when NOT to use this calendar (e.g. historical results), so it falls short of 5.

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

All QuantGeeks GEX tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?