Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

yahoo_finance_ticker_options_expiration

Fetch options chain data for a given expiration date of a Yahoo Finance ticker, returning calls and puts for analysis.

Instructions

Yahoo Finance options chain by expiration. Returns the calls and puts for one expiration of a Yahoo Finance symbol. expiration is a Unix timestamp, and the options endpoint lists the available ones in expiration_dates. The result is an options entry with expiration_date, calls and puts.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL
expirationYesUnix expiration timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the return shape (an `options` entry containing `expiration_date`, `calls`, and `puts`) and that the call is a lookup by a Unix timestamp, but omits auth requirements, rate limits, or data-freshness behavior expected of a finance endpoint.

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 the core purpose, then parameter context, then return shape. Every sentence earns its place with no padding, though the phrasing is slightly mechanical.

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?

With no output schema, the description steps in to describe the return (`expiration_date`, `calls`, `puts`), and it explains the Unix-timestamp parameter and its source. For a two-param read tool this is nearly complete; only auth/delay behavior is unaddressed.

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 both params are documented in the schema (symbol example AAPL, expiration as Unix timestamp). The description reinforces these meanings and adds the pointer that valid timestamps come from `expiration_dates`, but offers no format or validation 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 clear verb+resource: returns the calls and puts for one expiration of a Yahoo Finance symbol. It distinguishes itself from a generic options endpoint by emphasizing 'by expiration' and 'for one expiration,' but it never names the sibling (yahoo_finance_ticker_options) it complements, so differentiation is implicit rather than explicit.

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?

It hints at usage by noting that the endpoint lists available expirations in `expiration_dates`, implying the caller must obtain a valid expiration first, but it never states a when-to-use rule or names the sibling tool that provides those dates. Guidance is implied, not stated.

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