Skip to main content
Glama

Earnings calendar

events_calendar
Read-onlyIdempotent

Return earnings-release dates for one company or every company: confirmed dates are when an 8-K with Item 2.02 (results of operations) was accepted, with session bmo, dmh or amc; predicted dates are a model (the release a year earlier plus 364 days), labelled "expected (model)". Without from or to the window starts 30 days before as_of. Do not call a confirmed date an earnings call. Use it when asked when a company reports results, or which companies report in a window.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "ticker:AAPL"
    },
    "name": "events_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, inclusive (YYYY-MM-DD).
fromNoFirst date, inclusive (YYYY-MM-DD).
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 50, at most 1000).
cursorNoOpaque cursor from a previous page (data.next_cursor).
companyNoCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.
confidenceNoconfirmed: an 8-K Item 2.02 was filed; predicted: the cadence model.

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ company, event_type, date, session, confidence, label, fiscal_period, proof, known }], next_cursor, note }
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: confirmed dates are defined by an accepted 8-K Item 2.02 with session bmo, dmh, or amc, predicted dates come from a year-earlier-plus-364-days model, and results are labelled "expected (model)". It also discloses the default window behavior when from or to is omitted.

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-loads the core purpose, then supplies the definitions and usage rule without filler. Every sentence adds operational meaning, including the warning about earnings calls.

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?

Complete for a read-only calendar tool with full schema coverage, annotations, and an output schema. It covers methodology, defaults, and usage sufficiently for an agent to invoke it correctly.

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, but the description adds meaning for the temporal parameters by explaining the default window starts 30 days before as_of. It also explains the confirmed/predicted distinction for the confidence parameter beyond the enum labels.

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: return earnings-release dates for one company or every company. It clearly distinguishes confirmed 8-K Item 2.02 dates from model-predicted dates and warns against confusing them with earnings calls.

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 explicit usage contexts: when asked when a company reports results, or which companies report in a window. It does not name a sibling alternative such as calls_calendar, so it stops short of full when-not guidance.

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.

Resources