Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_calendar_results

Fetch Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits, filtered by start and end dates and paged with limit and offset.

Instructions

Yahoo Finance calendar results. Returns Yahoo Finance calendar rows for the path type: earnings, ipo, economic-events or splits. Narrow with start and end (YYYY-MM-DD, RFC3339 or Unix seconds) and page with limit (max 100) and offset. For earnings only, market_cap sets a minimum and filter_most_active (default true) filters. The response echoes the window and paging with the rows.

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

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose concrete traits: it is a read ('returns'), the default of filter_most_active is true, limit caps at 100, and the response echoes the window and paging alongside `rows`. It omits auth requirements, error behavior, and rate limits, so it is informative but not exhaustive.

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?

Purpose is front-loaded in the first sentence, followed by scoping, paging, and conditional details in a logical order. It is dense but each clause carries operational information, with minimal redundancy aside from echoing schema-provided detail.

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?

No output schema exists, and the description compensates by noting that the response echoes the window and paging with the `rows`. Combined with fully documented parameters and a required `type` enum, an agent has enough to invoke the tool correctly; only response-field detail is thin.

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 the schema already documents all seven parameters, making a 3 the baseline. The description mostly restates schema facts (date formats, max 100, default true, earnings-only scope) rather than adding new semantics, so it does not rise above baseline.

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 gives a specific verb and resource ('Returns Yahoo Finance calendar rows') and enumerates the four calendar types, so an agent knows exactly what this produces. It does not, however, differentiate itself from the sibling tool `yahoo_finance_calendars`, which appears closely related, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied through parameter scoping ('Narrow with start and end ... page with limit and offset') and the conditional 'For earnings only' clause, which tells the agent when two parameters apply. There is no explicit statement of when to prefer this tool over the sibling calendar tool or what prerequisites exist, so guidance remains partial.

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