tastytrade-mcp

List orders

list_orders

Retrieve orders for an account with filters for status, symbol, date range, and live-only working orders.

Instructions

List orders for an account. Use live_only for today's working orders.

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": {
      "account_number": "<account_number>"
    },
    "name": "list_orders"
  }
}

Input Schema

Name	Required	Description
`account_number`	Yes	The account number
`live_only`	No	Only return live (working) orders from the current session
`status`	No	Filter by order status
`underlying_symbol`	No	Filter by underlying symbol
`start_date`	No	Earliest order date, YYYY-MM-DD
`end_date`	No	Latest order date, YYYY-MM-DD
`per_page`	No	Results per page (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 10, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description must provide behavioral context. It only states the action without mentioning read-only nature, rate limits, pagination behavior, or error handling, leaving significant gaps.

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 sentences, front-loaded with the main action followed by a useful tip. No fluff or redundant information.

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 the rich input schema (100% parameter coverage) and no output schema, the description is adequate for basic use but lacks details on default behavior, sorting, or edge cases that an agent might need.

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 minimal extra value. The tip about live_only is marginally helpful but largely duplicates the schema description. No additional context for other parameters.

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 orders for an account, with a specific verb and resource. It distinguishes from siblings like get_order (singular) by implying plural listing.

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?

Only one hint is provided: 'Use live_only for today's working orders.' No explicit guidance on when to use this tool vs alternatives like get_order, nor any when-not or exclusion criteria.

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

Deploy Server