Skip to main content
Glama
Sign In

Tradier

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Tradier Option Expirations

tradier_option_expirations
Read-onlyIdempotent

List the available option expiration dates for . Returns an array of YYYY-MM-DD dates you can pass to tradier_option_chain. Example: tradier_option_expirations({ symbol: "AAPL", _apiKey: "your-token" })

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, which accurately describe the tool's safety. The description adds minimal behavioral information beyond the annotations, such as the return format, but does not contradict them.

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?

Two concise sentences and an example, with the action verb front-loaded. Every sentence serves a purpose, no redundancy.

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?

The description explains the return format (array of YYYY-MM-DD dates) and its downstream use, which is adequate for a simple list tool. However, it does not mention error cases or what happens if the symbol has no options.

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 description adds little new meaning. It includes an example showing symbol and _apiKey, but the schema already explains their purpose. The sandbox parameter is shown but not described. Baseline of 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?

The description clearly states the tool lists available option expiration dates for a symbol, with a specific verb 'List' and resource 'option expiration dates'. It distinguishes itself from siblings like tradier_option_chain and tradier_quote by specifying that the output is an array of dates to be passed to the chain.

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 suggests a sequential usage pattern by stating the output can be passed to tradier_option_chain, but it lacks explicit guidance on when to use or not use this tool, and does not mention prerequisites or alternatives.

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
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