Skip to main content
Glama

FinanceQuery

Options Chain

get_options
Read-onlyIdempotent

Get the options chain for a symbol. Provide an expiration timestamp to get a specific expiry, or omit for the nearest expiration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum contracts per side (calls/puts) per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor` (applied to both calls and puts); omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol
expirationNoExpiration date as Unix timestamp in seconds (optional; defaults to nearest expiration)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the default-expiry behavior, but says nothing about pagination cost, response size, or how calls/puts sides are returned — context the annotations do not supply.

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 short sentences with the primary action first and the optional-parameter rule second. No filler, no repetition, and the key decision (pass or omit expiration) is front-loaded.

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 five-parameter read tool with fully described schema fields and rich annotations and no output schema, the description covers the core call pattern. It could mention that results are paginated per side, but the cursor schema field already implies this.

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%, so symbol, expiration, limit, cursor, and fields are all already documented. The description's remark about expiration defaults merely restates the schema's 'defaults to nearest expiration', adding no new semantics.

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 and resource ('Get the options chain for a symbol'), which is unambiguous and clearly distinct from the profile, financials, and indicator siblings. It does not explicitly contrast with any related tool, but the purpose is self-evident.

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?

The description gives conditional guidance for the expiration parameter ('provide... or omit for the nearest expiration'), which is genuinely useful. It offers no guidance on when to choose this tool over alternatives or on how to use limit/cursor/fields for larger chains.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.