Crawlora MCP

yahoo_finance_calendar_results

Read-only

Fetch Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits. Use yahoo_finance_calendars to discover the calendar types and date ranges before requesting results.

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": {
      "type": "<type>"
    },
    "name": "yahoo_finance_calendar_results"
  }
}

Input Schema

Name	Required	Description
`end`	No	End date as YYYY-MM-DD, RFC3339, or Unix seconds.
`type`	Yes	Calendar type: earnings, ipo, economic-events, or splits.
`limit`	No	Result count, max 100.
`start`	No	Start date as YYYY-MM-DD, RFC3339, or Unix seconds.
`offset`	No	Result offset.
`market_cap`	No	Earnings-only market cap minimum.
`filter_most_active`	No	Earnings-only most-active filter.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and reach profile is covered. The description adds the available row types but says nothing about pagination, rate limits, or result caps (the schema's 'max 100' is never surfaced). Adequate but thin against already-rich annotations.

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?

Two sentences with zero waste: the fetch scope is front-loaded and the routing hint follows. Every clause earns its place.

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?

An output schema exists, so return values need not be explained. The description covers what is fetched, the permissible types, and the prerequisite discovery step; only minor behavioral detail (limits/pagination) is absent.

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 documented in the schema. The description restates the type values with slightly different spellings ('IPOs', 'economic events') than the schema's accepted values ('ipo', 'economic-events'), so it adds no reliable meaning beyond the schema.

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 verb (Fetch) and resource (Yahoo Finance calendar rows), then enumerates the four row types (earnings, IPOs, economic events, splits). It is clearly distinguishable from the sibling yahoo_finance_calendars, which is named as the discovery tool.

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?

Explicitly routes the agent: use yahoo_finance_calendars first to discover calendar types and date ranges before requesting results. This is a clear alternative/prerequisite statement, though it never states when NOT to use this tool.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?