Crawlora MCP

yahoo_finance_ticker_calendar

Read-only

Fetch calendar events associated with one Yahoo Finance symbol. Use yahoo_finance_calendars to discover calendar types and yahoo_finance_calendar_results for date-specific rows from a selected calendar.

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": {
      "symbol": "<symbol>"
    },
    "name": "yahoo_finance_ticker_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Yahoo Finance symbol such as AAPL.

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

A3.8/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 network profile is covered. The description adds the symbol-scoping constraint and the surrounding workflow, but says nothing about auth, rate limits, or result shape. With annotations carrying the safety profile and an output schema present, a 3 is appropriate.

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, zero waste: the purpose is front-loaded and the second sentence is purely routing information. Nothing needs trimming or reordering.

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 needn't be described, and annotations cover the safety profile. The description supplies the workflow context and symbol scoping. The only residual gap is not specifying what event categories the calendar returns, but that is minor given the routing to yahoo_finance_calendars.

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% and the single 'symbol' parameter is fully documented with an example (AAPL). The description only echoes the symbol scoping ('one Yahoo Finance symbol') without adding format or validation detail, so baseline 3 is correct.

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?

States a specific verb and resource with scope ('Fetch calendar events associated with one Yahoo Finance symbol'), and it names the two related calendar siblings so the agent can separate this symbol-level call from calendar-type discovery and date-row lookups. It stops short of clarifying what kind of events these are (earnings, dividends, splits), which several other yahoo_finance_ticker_* siblings also cover.

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 to discover calendar types and yahoo_finance_calendar_results for date-specific rows. This gives a clear three-step workflow. It doesn't state an explicit 'when not to use' or a prerequisite ordering, so it falls just short of a 5.

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?