Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_order_option_debit_spread

Place a vertical debit spread option order for bull call or bear put spreads, specifying option type, long/short OCC symbols, quantity, and net debit.

Instructions

Place a vertical debit spread option order.

For CALL: bull call spread. For PUT: bear put spread.

Args:
    account_hash: Account hash from schwab_account_numbers
    option_type: "CALL" or "PUT"
    long_symbol: OCC symbol for the leg you buy (main directional position)
    short_symbol: OCC symbol for the hedge/short leg
    quantity: Number of spread contracts
    net_debit: Net debit paid as a string (e.g. "3.00")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_hashYes
option_typeYes
long_symbolYes
short_symbolYes
quantityYes
net_debitYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. Description only states 'Place' an order with no disclosure of trade execution behavior, potential rejections, or margin implications. Does not describe what happens after placement.

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?

Very concise: two sentences plus a clean parameter list. No filler, all information is relevant. Front-loaded with the core purpose.

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

Completeness3/5

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

Explains basic role of each parameter but lacks context on how to obtain OCC symbols, prerequisites for account_hash, or the significance of net_debit. Output schema exists but is not referenced. Adequate for experienced users but incomplete for novices.

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 has 0% description coverage so description compensates by explaining each parameter: account_hash source, option_type, long_symbol (main position), short_symbol (hedge), quantity, net_debit with example. Adds value beyond schema titles and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it places a vertical debit spread option order and explains CALL vs PUT strategies. However, it does not explicitly differentiate from sibling tool 'schwab_order_option_credit_spread', which is a similar order type.

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 guidance on when to use this tool versus alternatives like credit spreads. No mention of prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Open-Agent-Tools/open-stocks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server