Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_cancel_all_stock_orders

Cancel all open equity orders in your Schwab account in one action.

Instructions

Cancel all open equity 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 beyond the basic action of cancellation. It lacks information on irreversibility, error scenarios, or rate limits, which are important for a destructive operation.

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 extremely concise with two short sentences and a parameter list. Every sentence provides necessary information without redundancy or fluff.

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?

While an output schema exists, the description omits important context such as the need to first obtain account_hash from schwab_account_numbers. The minimal nature leaves gaps for a mutation tool, making it adequate but not thorough.

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 description coverage is 0%, but the description adds meaning to both parameters: account_hash is identified as coming from schwab_account_numbers, and max_results is explained as a pre-filtering limit. This exceeds the schema's bare type information.

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 action ('Cancel all open equity orders') and the target resource ('for a Schwab account'), using specific verb and resource. It distinguishes well from siblings like cancel_stock_order_by_id (single order) and cancel_all_option_orders (different asset type).

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 when to use this tool (to cancel all stock orders) but does not explicitly contrast with alternatives or provide when-not-to-use guidance. No mention of prerequisites or conditions for effective use.

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