Skip to main content
Glama

Stock Expert AI Research

Stock Expert AI: earnings dates

stockexpertai_get_earnings
Read-onlyIdempotent

Earnings dates for one US stock the site covers: the next report date as listed by the data provider (nextReportConfirmed is true when that date falls inside the next 100 days — the window in which companies have normally announced it; longer-range dates are projections and can move) and the date of the last reported quarter. Consensus estimates, EPS actual vs estimate and surprise are not returned: full figures on the earnings page (canonicalUrl).

Use when: "when does NVDA report earnings", "when did AAPL last report", "NVDA earnings date". Args: ticker (string). Returns (structuredContent): { ticker, nextReportDate|null, nextReportConfirmed, lastReportDate|null, asOf, canonicalUrl, fullFigures, disclaimer }. Errors: "No earnings data for " when the ticker is not covered or no report history is cached. Derived output only: Stock Expert AI's own ratings, sentences and dates. Raw market figures (price, market cap, P/E, EPS, revenue) are not returned — full figures on the page (canonicalUrl). MoonshotScore is Stock Expert AI's educational research rating, not a buy or sell recommendation. Not financial advice. Not a registered investment adviser.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesUS ticker symbol, e.g. NVDA, BRK.B, AAPL (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining the semantics of nextReportConfirmed (true only inside a 100-day window; longer-range dates are projections that can move), documenting the exact error string 'No earnings data for <ticker>', and declaring the derived-output-only policy. That is meaningful behavioral context an agent would otherwise have to guess at, and nothing contradicts readOnlyHint/idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and well-sectioned (description, Use when, Args, Returns, Errors), which is good structure. However, the 'full figures on the page (canonicalUrl)' point is made twice, and the MoonshotScore disclaimer is boilerplate that does not apply to this tool's declared return fields, so not every sentence earns its place.

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?

There is no output schema, yet the description enumerates every returned field including nullability (nextReportDate|null, lastReportDate|null) and companion fields (asOf, canonicalUrl, disclaimer). Combined with the documented error case and the coverage caveat, an agent has enough to call this correctly and interpret the result.

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?

Only one parameter, and schema coverage is 100% — the schema already documents the ticker as a US symbol, case-insensitive, 1-10 chars, with examples like BRK.B. The description's 'Args: ticker (string)' merely restates this and adds no new meaning. Baseline 3 is appropriate given the schema does all the work.

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 and scope: 'Earnings dates for one US stock', enumerating exactly the two fields returned (next report date, last reported quarter date). The explicit exclusion ('Consensus estimates, EPS actual vs estimate and surprise are not returned') separates it from a summary-style sibling and tells an agent precisely what question this tool answers.

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?

The 'Use when:' block gives three concrete trigger phrasings ('when does NVDA report earnings', 'when did AAPL last report', 'NVDA earnings date'), which is strong positive guidance. It also steers the agent away from expecting full financials by pointing to the earnings page. It stops short of naming a sibling tool to use instead for EPS/revenue figures, so no explicit exclusion is made.

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