Place a limit sell order to sell a specified number of shares of a stock at a minimum price per share.
Places a limit sell order for a stock.
Args:
symbol: The stock symbol to sell (e.g., "AAPL")
quantity: The number of shares to sell
limit_price: The minimum price per share| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | ||
| quantity | Yes | ||
| limit_price | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose order behavior (e.g., day order vs GTC, prerequisites like share availability). Only parameter descriptions are given.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very concise: one-line purpose and parameter list. Front-loaded with action. Could include more context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Minimal but covers basics. Output schema exists but is not used to explain return values. For a simple order tool, it's adequate but lacks context for an agent to understand side effects or prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage; the brief parameter explanations in the description add basic meaning (e.g., symbol as stock symbol to sell), but lack details like expected formats or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool places a limit sell order, which is a specific verb+resource. It distinguishes from sibling tools like buy_stock_limit, sell_stock_market, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool over alternatives like sell_stock_market or sell_stock_stop_loss. User must infer from tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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