Skip to main content
Glama
Sign In
FinzData

FinzData

Official
by finzdata-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

earnings_dates

Fetch past earnings release dates for a ticker from SEC 8-K Item 2.02 filings, including report date, filing time (US Eastern), and before-open/after-close timing; free tier returns last 12 months.

Instructions

Past earnings release dates for a ticker from SEC 8-K Item 2.02 filings: report date, filing time (US Eastern) and whether it came before the open or after the close. No EPS or forecasts. On the free tier, only the last 12 months are returned.

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": {
      "ticker": "<ticker>"
    },
    "name": "earnings_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does add real behavioral context: the free-tier restriction to the last 12 months is a meaningful availability/limit disclosure, and the explicit 'No EPS or forecasts' sets scope expectations. It omits any auth or error behavior, but for a read-only lookup this is solid.

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?

Three tight sentences with no filler. The core resource and source are front-loaded, the scope exclusion follows, and the tier limitation is placed last where it belongs.

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 single-parameter, no-output-schema tool, the description covers what is returned, from where, and the coverage limitation, which is enough to call it correctly. It does not address behavior on invalid tickers or symbols with no filings, a minor gap.

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?

One required parameter at 0% schema description coverage. The description conveys the parameter's role ('for a ticker') but says nothing about expected ticker format, exchange suffixes, or case sensitivity, so it does not fully compensate for the empty schema description.

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 resource (past earnings release dates for a ticker), the authoritative source (SEC 8-K Item 2.02 filings), and the exact fields returned (report date, filing time US Eastern, before-open/after-close). This is immediately distinguishable from siblings like company_profile, fundamentals, or financial_statements.

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?

Usage is implied by the resource name rather than stated. The negative scoping line 'No EPS or forecasts' usefully redirects an agent away from this tool for estimate data, but no alternative sibling is named and no prerequisites or when-to-use condition is given.

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