Skip to main content
Glama

earnings-calendar

Retrieve upcoming US stock earnings reports with EPS estimates and market timing. Filter by ticker or set a date range up to 90 days ahead.

Instructions

Upcoming US stock earnings — report date, EPS estimate, pre/post-market timing. Filter by ticker or look N days ahead (1–90). Data: Alpha Vantage 3-month calendar, cached 2 hr.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoOptional. Ticker to filter by (e.g. NVDA, AAPL). Omit to get all earnings in the window.
days_aheadNoCalendar days ahead to include (1–90, default 7).
limitNoMax results (default 20, max 100). Ignored when symbol is provided (returns all matches).
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the data source (Alpha Vantage 3-month calendar), caching (2 hr), and the behavior of the limit parameter. Some missing details on error handling or 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?

The description is a single sentence but packs essential information. It is concise and front-loaded, though slightly dense. Could be broken into bullets for readability.

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?

Given no output schema and all optional parameters, the description covers purpose, filtering, data source, and caching. It lacks output format details, but is adequate for a calendar tool.

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%, but the description adds value by noting that limit is ignored when symbol is provided, which is not in the schema descriptions. This enhances understanding of parameter interactions.

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?

The description clearly states the tool provides upcoming US stock earnings with report date, EPS estimate, and timing. It also mentions filtering by ticker or days ahead, which distinguishes it from siblings like earnings-surprises and dividend-calendar.

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 description specifies how to filter (by ticker or days ahead) and notes the limit parameter is ignored when symbol is provided. However, it does not explicitly state when not to use this tool or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thebrierfox/the-stall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server