Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_order_option_credit_spread

Create a vertical credit spread option order by specifying the short and long legs, net credit, and quantity. Choose CALL for bear spread or PUT for bull spread.

Instructions

Place a vertical credit spread option order.

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

Args:
    account_hash: Account hash from schwab_account_numbers
    option_type: "CALL" or "PUT"
    short_symbol: OCC symbol for the leg you sell (collects premium)
    long_symbol: OCC symbol for the hedge/protective leg
    quantity: Number of spread contracts
    net_credit: Net credit received as a string (e.g. "2.00")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_hashYes
option_typeYes
short_symbolYes
long_symbolYes
quantityYes
net_creditYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Describes the legs and net credit but omits execution type, margin requirements, and error handling. With no annotations, more detail would be beneficial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with front-loaded purpose and bulleted args. Could add a brief usage note but overall efficient.

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?

Covers basic order mechanics but lacks clarification on net_credit per contract vs total and omits return value description despite output schema existing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Each parameter is explained beyond schema: account_hash source, option_type allowed values, short_symbol and long_symbol roles, quantity meaning, net_credit format example. Full compensation for 0% schema coverage.

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 'Place a vertical credit spread option order' and explains the two types (bear call spread for CALL, bull put spread for PUT). This distinguishes it from sibling tools like debit spreads.

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 for credit spreads but does not explicitly contrast with debit spreads or other order types. No guidance on 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