tastytrade-mcp

Get order

get_order

Retrieve the current state of a single order using its order ID and account number. Check order status, fills, or cancellations.

Instructions

Get the current state of a single order by id.

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>",
      "order_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`account_number`	Yes	The account number
`order_id`	Yes	The order id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description bears full burden. It states 'Get the current state', which implies a read-only operation with no side effects. However, it lacks explicit statements about safety, authorization needs, or rate limits. It adds minimal context beyond the obvious.

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?

The description is a single sentence, no fluff. It is concise and front-loaded with the key information (verb, resource, identifier).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and low complexity, the description should hint at return format or error handling. It simply says 'current state', which is vague. The agent lacks information about what the response will contain or what happens if the order is not found.

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% (both parameters have descriptions). The tool description adds no additional meaning beyond what the schema already provides. 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 action (Get), resource (current state of a single order), and identification method (by id). It effectively distinguishes from siblings like list_orders (list multiple) and cancel_order (different action).

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 implies the tool should be used when you need the state of a specific order, but it does not explicitly state when to use it versus alternatives or provide any exclusions. No mention of prerequisites or context.

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

Deploy Server