Skip to main content
Glama
Sign In
tastytrade-mcp

tastytrade-mcp

by bholzer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get account balances

get_balances

Retrieve current account balances including cash, net liquidating value, buying power, and margin usage. Input your account number to get real-time financial status.

Instructions

Get current balances for an account: cash, net liquidating value, buying power, margin usage, etc.

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_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_numberYesThe account number, e.g. 5WT00001

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so the description carries the full burden. It indicates a read operation ('get current balances') but does not disclose potential side effects, rate limits, permissions, or data caching. Listing example outputs adds some transparency but incomplete.

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?

Single sentence, front-loaded with the primary purpose. No redundant words, efficient and clear.

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?

For a simple one-parameter tool with no output schema, the description covers what it returns (various balances). However, the 'etc.' is vague, and there is no mention of the return format or structure.

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?

With 100% schema coverage and only one parameter, the description adds no new meaning beyond 'for an account'. The schema already documents account_number format. Baseline 3 applies.

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 'Get' and specifies the resource 'current balances for an account' with examples like cash, net liquidating value, buying power, margin usage, etc. This distinguishes it from sibling tools like get_accounts or get_positions.

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?

No explicit guidance on when to use this tool versus alternatives. It implies use for an account but does not provide context on when to prefer get_balances over get_accounts or other similar tools.

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