Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Place Crypto Order

place_crypto_order
Destructive

Place cryptocurrency buy or sell orders by symbol, specifying quantity or dollar amount, with market, limit, or stop-limit types.

Instructions

Place a cryptocurrency order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyNoNumber of coins/tokens. Mutually exclusive with notional.
sideYes"buy" or "sell".
typeNo"market", "limit", or "stop_limit".market
symbolYesCrypto pair (e.g., "BTC/USD", "ETH/USD").
notionalNoDollar amount to trade. Mutually exclusive with qty. Only valid for market orders.
stop_priceNoRequired for stop_limit orders.
limit_priceNoRequired for limit and stop_limit orders.
time_in_forceNo"gtc" (default) or "ioc". Crypto does not support "day" or "fok".gtc
client_order_idNoUnique idempotency key. If the request times out, you can safely retry with the same value — the API will reject duplicates. Recommended for every order.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.3.2
    • addedInput schema / properties / client_order_id / description
      Added value: +"Unique idempotency key. If the request times out,\n             you can safely retry with the same value — the API\n             will reject duplicates. Recommended for every order."
    • addedInput schema / properties / limit_price / description
      Added value: +"Required for limit and stop_limit orders."
    • addedInput schema / properties / notional / description
      Added value: +"Dollar amount to trade. Mutually exclusive with qty.\n      Only valid for market orders."
    • addedInput schema / properties / qty / description
      Added value: +"Number of coins/tokens. Mutually exclusive with notional."
    • addedInput schema / properties / side / description
      Added value: +"\"buy\" or \"sell\"."
    • addedInput schema / properties / stop_price / description
      Added value: +"Required for stop_limit orders."
    • addedInput schema / properties / symbol / description
      Added value: +"Crypto pair (e.g., \"BTC/USD\", \"ETH/USD\")."
    • addedInput schema / properties / time_in_force / description
      Added value: +"\"gtc\" (default) or \"ioc\". Crypto does not\n           support \"day\" or \"fok\"."
    • addedInput schema / properties / type / description
      Added value: +"\"market\", \"limit\", or \"stop_limit\"."
  2. Addedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds no behavioral context beyond the word 'place'—no mention of live trading impact, order execution behavior, or retry semantics. It does not contradict the annotations.

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 and free of filler, which is good, but it is terse to the point of adding little value beyond the tool name. It is not poorly structured, but brevity here is under-specification rather than effective concision.

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?

For a high-stakes order tool with 9 parameters, a single generic sentence is insufficient. The schema covers parameter syntax, but the description offers no guidance on order type selection, risk warnings, or when this tool is appropriate relative to similar order tools.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The tool description itself adds no parameter meaning, but the schema thoroughly documents qty, notional, order types, stop/limit prices, time-in-force, and idempotency keys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('place') and a clear object ('cryptocurrency order'), which distinguishes it from stock and option order tools by asset class. However, it is essentially the title restated and does not explicitly name or contrast sibling tools.

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?

There is no guidance on when to use this tool versus place_stock_order or place_option_order. The asset class is implied by 'crypto', but no explicit context, exclusions, or alternatives are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools