tastytrade-mcp

Replace order

replace_order

Modify a working order's price, order type, or time in force without affecting other order details. Use to adjust pricing or duration of a pending order.

Instructions

Modify a working order's price, type, or time in force. Only the provided fields change; legs cannot be modified (cancel and re-create instead).

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": "replace_order"
  }
}

Input Schema

Name	Required	Description
`account_number`	Yes	The account number
`order_id`	Yes	The order id to modify
`price`	No	New price as a decimal string
`price_effect`	No	New price effect
`order_type`	No	New order type
`time_in_force`	No	New time in force
`stop_trigger`	No	New stop trigger price

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 10, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations provided, so description must fully disclose behavior. It states 'Only the provided fields change' and highlights the leg restriction, but does not mention prerequisites (e.g., order must be working), permissions, or error cases. Partial transparency.

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 tightly written sentences. First sentence states purpose and scope. Second sentence provides a critical constraint. No unnecessary words, well-structured.

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 7 parameters, 3 enums, and no output schema, the description covers the main functional constraints. It lacks details on order state requirements but is otherwise adequate for a replace-order operation.

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 coverage is 100% with individual parameter descriptions. The description adds overarching context: it modifies price, type, or time in force, and that legs are not modifiable. This adds value beyond the schema's per-parameter details.

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 modifies a working order's price, type, or time in force, and distinguishes from siblings like create_order (creation) and cancel_order (cancellation). It also explicitly notes that legs cannot be modified, adding precision.

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?

Provides explicit when-to-use: modifying a working order's price, type, or time in force. Also gives clear when-not-to-use: legs cannot be modified, advising to cancel and re-create instead. This effectively guides the agent away from incorrect usage.

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

Deploy Server