tastytrade-mcp

Get positions

get_positions

Retrieve all open positions for a specified account, with optional filters by underlying or symbol.

Instructions

List all open positions for an account, optionally filtered by symbol or underlying.

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

Input Schema

Name	Required	Description
`account_number`	Yes	The account number
`underlying_symbol`	No	Filter by underlying symbol, e.g. AAPL
`symbol`	No	Filter by exact instrument symbol
`include_marks`	No	Include current mark prices (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states it lists open positions (a read operation) but lacks details on safety, rate limits, or error handling. The description adds minimal value 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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose.

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?

With no output schema and no annotations, the description is minimal. It does not explain return format, pagination, error conditions, or authentication requirements, leaving gaps for an agent needing full context.

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 baseline is 3. The description mentions optional filtering by symbol or underlying, which aligns with the schema but does not add extra meaning beyond the parameter descriptions themselves.

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 verb 'list', the resource 'open positions', and the scope 'for an account', with optional filters. It is specific and distinguishes itself from sibling tools like get_orders or get_quotes.

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 usage (listing positions) but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisite conditions.

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

Deploy Server