Skip to main content
Glama

TradingMCP

by io.github.atilaahmettaner
OverviewDiscussionsAdmin

Options Chain

stock_options_chain
Read-only

Full options chain (calls + puts) for a US stock symbol and one expiry.

Use this when the user asks "what's the options chain for X?", "show me
AAPL puts expiring next Friday", or wants to inspect bid/ask/IV/volume on
a specific strike. If no expiry is provided, returns the nearest expiry
so Claude can quote it back and ask "want a different one?".

Args:
    symbol: US stock symbol — AAPL, NVDA, TSLA, SPY, etc.
    expiry: Optional ISO date (YYYY-MM-DD). Must match one of the
        `available_expiries` Yahoo returns; otherwise returns an error
        with the list of valid dates.

Returns:
    - underlying_price, underlying_change_pct
    - requested_expiry, available_expiries (list of YYYY-MM-DD)
    - call_count, put_count
    - calls: list of {strike, last_price, bid, ask, volume,
      open_interest, implied_volatility, in_the_money, expiration}
    - puts: same shape as calls

Input Schema

NameRequiredDescriptionDefault
expiryNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the nearest-expiry default when no expiry is passed, and the error-plus-valid-dates response when an expiry does not match available_expiries. It omits rate limits or data freshness, hence not a 5.

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?

Front-loaded with the one-line purpose, followed by usage triggers, Args, and Returns in clearly labeled blocks. The length is justified by the fact that there is no output schema, so the return-field enumeration must live here. No filler sentences.

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

Completeness5/5

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

With no output schema, no param descriptions, and no enums, the description compensates fully: it documents both parameters, the default/error behavior, and the exact shape of the returned calls/puts objects plus counts and underlying price. An agent has everything needed to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load and it does: symbol is defined as a US stock symbol with examples (AAPL, NVDA, TSLA, SPY), and expiry is defined as an optional ISO date (YYYY-MM-DD) that must match one of available_expiries. Both parameters are fully disambiguated beyond the bare schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full options chain (calls + puts)') scoped to a US stock symbol and a single expiry. This clearly distinguishes it from the sibling stock_options_unusual_activity, which serves a different purpose. An agent can identify it without opening the schema.

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?

Gives concrete user-phrasing triggers ('what's the options chain for X?', 'show me AAPL puts expiring next Friday') and describes the no-expiry fallback (returns nearest expiry and asks the user). It does not name a distinguishing alternative like stock_options_unusual_activity, so it stops short of a full when-not/alternatives statement.

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

All TradingMCP toolsInspect
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