Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_option_trades

Retrieve historical option contract trades using symbols and filters for date range, sort order, limit, and pagination to analyze market activity.

Instructions

Retrieves historical trade data for one or more option contracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoThe inclusive end of the interval. Format: RFC-3339 or YYYY-MM-DD. Default: the current time if the user has a real-time access for the feed, otherwise 15 minutes before the current time.
sortNoSort data in ascending or descending order.
limitNoThe maximum number of data points to return in the response page. The API may return less, even if there are more available data points in the requested interval. Always check the `next_page_token` for more pages. The limit applies to the total number of data points, not per symbol!
startNoThe inclusive start of the interval. Format: RFC-3339 or YYYY-MM-DD. Default: the beginning of the current day, but at least 15 minutes ago if the user doesn't have real-time access for the feed.
symbolsYesA comma-separated list of contract symbols with a limit of 100.
page_tokenNoThe pagination token from which to continue. The value to pass here is returned in specific requests when more data is available, usually because of a response result limit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.3.2
    • addedInput schema / properties / sort / allOf
      Added value: +[
+  {
+    "default": "asc",
+    "description": "Sort data in ascending or descending order.",
+    "enum": [
+      "asc",
+      "desc"
+    ],
+    "type": "string"
+  }
+]
    • removedInput schema / properties / sort / default
      Removed value: -"asc"
    • removedInput schema / properties / sort / enum
      Removed value: -[
-  "asc",
-  "desc"
-]
    • removedInput schema / properties / sort / x-go-name
      Removed value: -"TypeSort"
  2. Addedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral disclosure burden, but it only states the basic retrieval action and resource scope. It does not disclose pagination behavior, default time-window behavior depending on real-time access, or the cross-symbol limit semantics, all of which affect how the tool is invoked.

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?

A single focused sentence that front-loads the core action and resource. There is no filler or 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?

Given a fully documented input schema and an output schema, a one-sentence description is largely sufficient for a straightforward historical data retrieval tool. It lacks only the routing guidance to alternatives, which prevents a perfect score.

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 the schema already documents all six parameters in detail. The description adds no parameter-specific meaning beyond the phrase 'one or more option contracts,' which reinforces the required symbols parameter but does not exceed the schema.

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 names a specific verb ('Retrieves'), a precise resource ('historical trade data'), and a scope ('one or more option contracts'). It also distinguishes this from nearby siblings like get_option_latest_trade (historical vs. latest) and get_option_bars (trades vs. bars).

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

Usage Guidelines2/5

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

The description gives no guidance on when to choose this endpoint over the related get_option_latest_trade, get_stock_trades, or get_crypto_trades. An agent must infer usage from the name and schema alone.

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