Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_options

Fetch Yahoo Finance option expiration dates and the current calls/puts chain for a ticker symbol to research or plan derivatives trades.

Instructions

Yahoo Finance options chain. Returns the option expiration dates (expiration_dates, as Unix timestamps) and the current option chain for a Yahoo Finance symbol such as AAPL. Each options entry has an expiration_date with its calls and puts; underlying describes the underlying security.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape well (expiration_dates as Unix timestamps, options entries with calls/puts, underlying), but says nothing about read-only nature, auth, rate limits, or pagination of a potentially large chain.

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?

Three tight sentences, front-loaded with what the tool is, followed by return structure. No filler; every clause carries information about output shape.

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?

For a single-param read tool with no output schema, the description compensates by describing the returned fields (expiration_dates, options, calls, puts, underlying). It stops short of covering volume/size or behavior under missing symbols, but is otherwise adequate.

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% and the single symbol param is already documented there with the same 'such as AAPL' example. The description adds no format, exchange, or ticker-suffix detail beyond the schema, so baseline 3 applies.

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 (returns) and resource (options chain / expiration dates) plus the input symbol. Clear enough to distinguish from generic quote tools, though it does not differentiate itself from the sibling yahoo_finance_ticker_options_expiration, which apparently returns only the dates.

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 when-to-use guidance, prerequisites, or named alternatives. With a sibling (yahoo_finance_ticker_options_expiration) that overlaps in scope, the agent gets no help choosing between them.

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