Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

by Open-Agent-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

schwab_sell_stock_limit

Sell shares of a stock at a specified limit price. Set the number of shares and target price to execute the order when the market reaches your price.

Instructions

Place a limit sell order for stock.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_hashYes
symbolYes
quantityYes
priceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided; description fails to disclose behavioral traits such as order execution guarantees, partial fills, or cancellation policies, leaving the agent without critical behavioral context.

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

Conciseness3/5

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

The description is very short but lacks structure; it is concise yet sacrifices completeness, offering only a single line plus a parameter list without explanatory context.

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?

Despite having an output schema, the description does not mention return values or order outcomes (e.g., order ID, status), leaving the agent uninformed about what to expect after invocation.

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

Parameters2/5

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

With 0% schema description coverage, the description adds minimal value beyond parameter names (e.g., 'price: Limit price' is tautological). No further semantics or constraints are provided.

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 limit sell order for stock' with a specific verb and resource, distinguishing it from sibling tools like market or stop orders.

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 limit vs market or stop sell orders; lacks context for choosing among siblings without additional knowledge.

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