Skip to main content
Glama

Tradier

by io.github.pipeworx-io

Tradier Option Chain

tradier_option_chain
Read-onlyIdempotent

Get the option chain (strikes, greeks, IV, open interest) for expiring . Returns every call and put at that expiration with bid/ask/last, volume, open interest, and greeks (delta/gamma/theta/vega/IV). Example: tradier_option_chain({ symbol: "AAPL", expiration: "2026-01-16", _apiKey: "your-token" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesUnderlying ticker symbol, e.g. "AAPL", "SPY", "TSLA"
_apiKeyYesTradier access token (free with a funded Tradier brokerage account, or a sandbox token)
sandboxNoUse the Tradier sandbox environment (sandbox.tradier.com) instead of production. Default false.
expirationYesExpiration date in YYYY-MM-DD format, e.g. "2026-01-16" (use tradier_option_expirations to list valid dates)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-tradier-api-key",
+    "expiration": "2026-01-16",
+    "symbol": "AAPL"
+  },
+  {
+    "_apiKey": "your-tradier-api-key",
+    "expiration": "2026-02-20",
+    "sandbox": true,
+    "symbol": "SPY"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description carries less burden for safety. It adds value by detailing the return fields (greeks, open interest, etc.) and provides an example call, which helps agents understand expected output.

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?

Description is two sentences plus an example, perfectly front-loaded with the core purpose. Every sentence adds value, and the example clarifies usage. No wasted words.

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?

Given no output schema, the description adequately explains what is returned (all calls/puts, bid/ask/last, volume, open interest, greeks). The example further helps. Could mention pagination or rate limits, but overall sufficient for most use cases.

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 all parameters are already described in the input schema. The description adds an example and reiterates the _apiKey and expiration format, but does not provide new semantic meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool retrieves an option chain for a given symbol and expiration, and lists the specific data returned (strikes, greeks, IV, open interest, bid/ask/last, volume). This distinguishes it from sibling tools like tradier_quote (single quote) and tradier_option_expirations (list expirations).

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?

The description implies when to use (when you need full option chain data for a specific symbol and expiration). However, it does not explicitly mention when not to use or provide direct alternatives. Given the clear sibling tool names, this is still effective guidance.

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

All Tradier toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Multiple tools share overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and the five polymarket_* tools cover heavily overlapping territory. An agent must read lengthy descriptions to distinguish between them, and pairs like validate_claim vs ask_pipeworx_grounded or discover_tools vs suggest_questions have fuzzy boundaries.

Naming Consistency2/5

Naming is wildly inconsistent: verb_noun (compare_entities, discover_tools), bare verbs (forget, remember, subscribe), noun phrases (entity_profile, recent_alerts, pipeworx_feedback), prefixed families (tradier_*, polymarket_*) and suffixed variants (ask_pipeworx_beta, ask_pipeworx_grounded). There is no single predictable convention across the set.

Tool Count2/5

34 tools is far beyond the 15-25 heavy range, and the count is inflated by near-duplicates like ask_pipeworx/ask_pipeworx_beta and five polymarket edge tools. The server mixes several unrelated domains (Tradier quotes/options, Pipeworx research, Polymarket analysis, memory, subscriptions, web utilities), making the scope feel unbounded.

Completeness2/5

For a server named Tradier, having only quote and option-chain endpoints is a significant gap—no historical data, account, positions, or order execution. The Pipeworx/Polymarket side is more complete, but the inclusion of unrelated utilities like generate_llms_txt and scan_dependency means no single domain is fully served.

Resources