Skip to main content
Glama

FinanceQuery

Market-Wide Event Calendar

get_market_calendar
Read-onlyIdempotent

Get a market-wide event calendar over a date range: earnings, IPOs, dividends, splits, economic releases, market holidays, or live exchange open/closed status. Unlike get_calendar (per-symbol), this spans the whole market.

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": {
      "kind": "<kind>"
    },
    "name": "get_market_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD); ignored by market-holiday/market-status
fromNoStart date (YYYY-MM-DD); ignored by market-holiday/market-status
kindYesWhich market-wide calendar to fetch: earnings | ipo | dividend | split | economic | market-holiday | market-status
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and freshness profile is mostly covered upstream. The description adds the date-range scoping but nothing about rate limits, result size, or what live market-status actually returns; the note that from/to are ignored for certain kinds duplicates the schema.

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?

Two tightly written sentences: the capability and its kinds come first, then the sibling differentiator. No redundant framing or filler, and the whole definition is front-loaded with the actionable information.

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?

For a read-only listing tool with fully documented parameters and annotation coverage, the description is nearly complete, and the kind parameter is self-describing. Missing is any hint about output shape or volume, which matters somewhat since there is no output schema, keeping it just under a 5.

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%, with each parameter documented including the enumerated kind values and the note that from/to are ignored for market-holiday and market-status. The description adds no syntax or format detail beyond the schema, 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 ('Get a market-wide event calendar') plus the exact scope ('over a date range') and enumerates the event types covered. It explicitly contrasts itself with get_calendar (per-symbol), so an agent can distinguish the two without opening either schema.

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?

Names the alternative tool get_calendar and the differentiator (per-symbol vs whole market), which is clear routing guidance. It stops short of saying when to prefer market-holiday versus market-status versus earnings for overlapping needs, leaving the kind selection to the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.