Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

schwab_buy_stock_market

Place a market buy order for stocks using your Schwab account. Specify the account hash, stock symbol, and number of shares to execute the trade.

Instructions

Place a market buy order for stock.

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

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. The description only states 'market buy order' without disclosing behaviors like price slippage, partial fills, or execution guarantees. Minimal transparency.

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?

Short, front-loaded sentence with parameter list. No wasted words, though could include more details without becoming verbose.

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?

Adequate for basic usage but lacks prerequisites (e.g., getting account_hash from another tool) and order lifecycle info. Output schema may help but not shown.

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?

Schema description coverage is 0%. The description lists parameter names and hints at account_hash source but adds little meaning beyond names. No format or constraints.

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 buy order for stock' – a specific verb and resource. It distinguishes from siblings like limit orders and sell 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 this vs alternatives (e.g., limit orders, options). The description gives no context for tool selection among many similar siblings.

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