Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_cancel_all_option_orders

Cancel all open option orders in a Schwab account to clear pending trades and avoid unintended executions.

Instructions

Cancel all open option orders for a Schwab account.

Args:
    account_hash: Account hash from schwab_account_numbers
    max_results: Maximum orders to fetch before filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_hashYes
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as destructiveness, authentication needs, rate limits, or side effects. 'Cancel all' implies destructive action but confirmation is missing.

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?

The description is very short and front-loaded with the purpose. It efficiently conveys the core action, though it could include a sentence on usage without becoming verbose.

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?

The tool cancels all open option orders, but the description does not explain what happens after execution, return values, or idempotency. With no output schema shown and no annotations, the description is incomplete for full understanding.

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 0%, but the description adds meaning by specifying that account_hash comes from schwab_account_numbers and max_results is used for fetching before filtering. This provides context beyond the schema.

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 cancels all open option orders for a Schwab account, using a specific verb and resource. It distinguishes from siblings like cancel_all_stock_orders and cancel_option_order_by_id.

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 is provided on when to use this tool versus alternatives like cancel_option_order_by_id. The description only lists arguments without usage context.

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