Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Option Chain by Date

option_chain_info_by_date
Read-onlyIdempotent

Get all option contracts for a given expiry date, including calls and puts, with strike price, contract type, and days to expiry. Filter by direction or standard contracts only.

Instructions

Get the option contract list for one expiry date. Returns one entry per contract (calls and puts are NOT paired): {symbol, expiry_date, strike_price, direction (Call/Put), option_type (Monthly/Weekly/Quarterly), standard_attr (Normal/Old), days_to_expiry}. Filter on direction to split calls from puts, and pass standard_only=true to drop the legacy post-corporate-action contracts. Carries no prices or Greeks — pass the symbols to option_quote for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
dateYesExpiry date (yyyy-mm-dd). Required — list the tradable ones with `option_chain_expiry_date_list`.
symbolYesUnderlying security symbol, e.g. "AAPL.US". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.
standard_onlyNoReturn standard contracts only. Omitted or false returns everything, including the legacy contracts left over from a corporate action (`standard_attr: "Old"`), which are rarely what a caller wants.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • changedInput schema / properties / date / description
      Previous value: -"Date (yyyy-mm-dd)"New value: +"Expiry date (yyyy-mm-dd). Required — list the tradable ones with\n`option_chain_expiry_date_list`."
    • addedInput schema / properties / standard_only
      Added value: +{
+  "description": "Return standard contracts only. Omitted or false returns everything,\nincluding the legacy contracts left over from a corporate action\n(`standard_attr: \"Old\"`), which are rarely what a caller wants.",
+  "type": "boolean"
+}
    • changedInput schema / properties / symbol / description
      Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Underlying security symbol, e.g. \"AAPL.US\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."
  2. Changed1 schema field changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolDateParam"
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds substantial behavioral context beyond that: the response is one entry per contract with calls and puts unpaired, the default behavior of standard_only (omitted means legacy 'Old' contracts are included, which are 'rarely what a caller wants'), and the canvas callback 'returns an empty record, not an error' for padded codes. It sets clear expectations about what is absent (no prices/Greeks).

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?

Three sentences with zero waste: the first states purpose and return shape, the second delivers filtering guidance, the third sets expectations and routes to a sibling tool. Key information is front-loaded — the agent learns what the tool does and what it returns in the opening sentence. Every sentence earns its place.

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, the description's full field list ({symbol, expiry_date, strike_price, direction, option_type, standard_attr, days_to_expiry}) carries the burden of documenting return values, and it does so completely. All four parameters are documented in the schema, annotations cover the safety profile, and the description addresses edge behavior, default filtering, and companion tools. Nothing an agent needs to correctly invoke this tool is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all four parameters, setting the baseline at 3. The description adds genuine value beyond schema by explaining how to use parameters to get desired results: filtering on direction to split calls from puts, and passing standard_only=true to drop the legacy post-corporate-action contracts. It also maps output fields (direction, standard_attr) to parameter usage, which helps the agent reason about the contract data.

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 first sentence names a specific verb and resource with precise scope: 'Get the option contract list for one expiry date.' It distinguishes from siblings by detailing the exact return shape (one entry per contract, calls/puts NOT paired) and explicitly stating what it does NOT do ('Carries no prices or Greeks'), which separates it from option_quote and option_volume. An agent can tell this tool apart from its nearest siblings without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly routes to option_quote for prices/Greeks ('pass the symbols to option_quote for those') and the schema's date parameter directs users to option_chain_expiry_date_list to find tradable dates. It also gives concrete invocation guidance: filter on direction to split calls from puts, and pass standard_only=true to exclude legacy contracts. When-to-use and where-else-to-go are both stated explicitly rather than left to inference.

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