Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

yahoo_finance_calendar_results

Retrieve global Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits by type and date range.

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
filter_most_activeNoEarnings-only most-active filter, default true
limitNoResult count, max 100
market_capNoEarnings-only market cap minimum
offsetNoResult offset
startNoStart date as YYYY-MM-DD, RFC3339, or Unix seconds
typeYesCalendar type: earnings, ipo, economic-events, or splits
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only says 'returns rows' without mentioning pagination, rate limits, data freshness, or any side effects. For a tool with 7 parameters, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but lacking structure. It front-loads the purpose but misses opportunities to provide quick-reference hints for parameters or usage.

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

Completeness2/5

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

The tool has 7 parameters and no output schema, yet the description fails to explain the return format, pagination limits, or how parameters interact. For a calendar results tool, more context on date range handling and result ordering is needed.

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 each parameter. The description adds value by listing the event types but does not explain parameter relationships or constraints 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 clearly states the tool returns 'global Yahoo Finance calendar rows for earnings, IPOs, economic events, or splits,' specifying both the resource and event types. However, it does not differentiate from siblings like 'yahoo_finance_calendars' or ticker-specific calendar tools.

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 explicit guidance on when to use this tool versus alternatives. The sibling list includes 'yahoo_finance_calendars' and numerous ticker-specific tools, but the description provides no context for choosing this one.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server