Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_sell_stock_market

Execute a market sell order for a specified stock symbol and quantity using a Schwab account hash. Quickly liquidate positions at current market price.

Instructions

Place a market sell order for stock.

Args:
    account_hash: Account hash from schwab_account_numbers
    symbol: Stock ticker symbol
    quantity: Number of shares to sell

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_hashYes
symbolYes
quantityYes

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 lacks disclosure of execution behavior (e.g., price slippage, order types, risks). For a trading tool, this is insufficient transparency.

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?

Concise: four lines covering purpose and three parameters with no superfluous text. Every sentence adds value.

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?

Lacks context like error handling, order lifecycle, or prerequisites. However, output schema exists (unknown content), so return values may be covered. Adequate but incomplete for a complex trading action.

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 coverage is 0%, so description must compensate. It briefly explains each parameter: account_hash from another tool, symbol as ticker, quantity as number of shares. Adds value beyond schema names.

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 market sell order for stock,' which is a specific verb-resource combination. It distinguishes from sibling tools like schwab_sell_stock_limit and schwab_buy_stock_market.

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 vs alternatives. For example, no mention that market orders execute immediately vs limit orders, or that it's for stocks not options. Sibling tools like sell_stock_limit and buy_stock_market exist.

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