Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_earnings_dates

Retrieve earnings dates for a Yahoo Finance ticker symbol to plan around upcoming reports. Supports limit and offset paging, returning each row as JSON.

Instructions

Yahoo Finance earnings dates. Returns earnings-date rows for a Yahoo Finance symbol, taken from Yahoo's earnings calendar table. limit (max 100) and offset page the rows. Each row is keyed by the table's column names, such as Earnings Date. Returns an upstream error when Yahoo does not serve the table.

Input Schema

NameRequiredDescriptionDefault
limitNoResult count, max 100
offsetNoResult offset
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits beyond the schema: pagination via limit/offset, that rows are keyed by the upstream table's column names, and that an upstream error is returned when Yahoo does not serve the table. It omits auth requirements, rate limits, and whether results are cached, so the coverage is partial.

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?

Four short sentences, front-loaded with the core purpose and then paging and error behavior. Nearly every sentence earns its place; the 'keyed by column names' sentence is useful for interpreting rows given the absence of an output schema.

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 simple paginated read tool with no output schema, the description adequately covers return shape (table-column-keyed rows) and failure behavior. The main gap is the lack of differentiation from the sibling earnings/calendar tools, which matters given how many exist.

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 coverage is 100%, so the schema already documents symbol, limit, and offset. The description only restates the max-100 cap and that the two parameters page the rows, adding no syntax or format detail beyond the schema. Baseline 3 applies when structured fields do the heavy lifting.

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 states a specific verb and resource: it returns earnings-date rows for a Yahoo Finance symbol, drawn from Yahoo's earnings calendar table. It is clear what the tool does, but it never distinguishes itself from the very close sibling yahoo_finance_ticker_earnings (nor yahoo_finance_ticker_calendar), so an agent cannot tell them apart from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the near-identical siblings. Usage is only implied by the resource name. For a domain with several overlapping earnings/calendar tools, this leaves the routing decision entirely to inference.

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