Skip to main content
Glama

FinanceQuery

Upcoming Events for Symbols

get_calendar
Read-onlyIdempotent

Get a time-sorted calendar of upcoming financial events (earnings with estimates, ex-dividend and dividend-payment dates, options expirations, and — when FRED is configured — market-wide economic releases) across multiple symbols. Answers 'what's coming up for my portfolio?' in one call.

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": {
      "symbols": "<symbols>",
      "range": "<range>"
    },
    "name": "get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesForward time window: 1d|5d|1mo|3mo|6mo|1y|2y|5y|10y|ytd|max (default: 1mo)
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolsYesComma-separated list of ticker symbols (e.g., "AAPL,MSFT,TSLA")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that results are time-sorted, span multiple symbols in one call, and that economic releases are conditional on FRED being configured — a feature-gated behavior an agent cannot learn from structured fields. It does not mention limits, maximum symbol count, or coverage of empty results.

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?

Two sentences, front-loaded with the resource and its contents, with an immediately useful framing sentence at the end. The long parenthetical enumeration of event types is dense but each item carries selection value, so little is wasted.

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 job of telling the agent what comes back (which event categories, sorted by time, across symbols) and one environment-dependent caveat. Missing only minor operational details such as result limits or behavior for symbols without events.

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 range enumerations and symbol format already documented in the schema, so the baseline is 3. The description reinforces that symbols are plural/aggregated and that the window is forward-looking, but adds no new detail on syntax or on the meaning of the optional fields filter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (upcoming financial events calendar) and enumerates the event types included — earnings with estimates, ex-dividend/dividend-payment dates, options expirations, and economic releases. It is clearly distinguishable from generic market-calendar or fundamentals tools, though it never explicitly contrasts itself with siblings like get_market_calendar or get_dividends.

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

Usage Guidelines3/5

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

It supplies a concrete usage framing ("Answers 'what's coming up for my portfolio?' in one call"), implying this is the aggregate/preferred query over per-symbol calls for forward-looking events. However, there is no explicit when-not guidance and no named alternative for related queries such as historical dividends or the market trading calendar.

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.