Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_calendar_results

Retrieve Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits with date filters and market cap limits. Get structured JSON for financial event research.

Instructions

Yahoo Finance calendar results. Returns global Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd date as YYYY-MM-DD, RFC3339, or Unix seconds
typeYesCalendar type: earnings, ipo, economic-events, or splits
limitNoResult count, max 100
startNoStart date as YYYY-MM-DD, RFC3339, or Unix seconds
offsetNoResult offset
market_capNoEarnings-only market cap minimum
filter_most_activeNoEarnings-only most-active filter, default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "earnings",
+  "ipo",
+  "economic-events",
+  "splits"
+]
  2. Addedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, but it only states that the tool returns rows. It does not disclose pagination behavior, default filters, date-range handling, or any operational traits, leaving significant behavior unspecified.

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 two-sentence description is compact and front-loads the resource, but the opening phrase 'Yahoo Finance calendar results' largely restates the tool name before adding substantive content. There is no wasted wording, though the first sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no annotations and no output schema, the description provides only a high-level statement of what is returned. The schema compensates for parameter details, but the description lacks usage context, pagination notes, or behavioral warnings, making it minimally complete.

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 description coverage is 100%, so all seven parameters are already documented with descriptions. The description adds only the 'global' scope qualifier and lists the enum values in prose, providing no extra parameter-level meaning beyond the schema.

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: 'Returns global Yahoo Finance calendar rows' with explicit calendar types (earnings, IPOs, economic events, splits). The 'global' qualifier hints at differentiation from ticker-specific calendar siblings, though it does not name them.

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?

No guidance is given on when to choose this tool over alternatives such as yahoo_finance_ticker_calendar or yahoo_finance_calendars. The description implies a global-calendar use case but leaves all selection logic 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