Skip to main content
Glama
Public.com MCP Server

Public.com MCP Server

Official
by PublicDotCom

place_short_order

Places an equity short-sale order for a ticker and share quantity, with market, limit, stop, or on-close types and DAY/GTD timing. Executes a real trade; run preflight validation first.

Instructions

Place an equity short-sale order.

⚠️ This executes a real trade. Consider running preflight_short_order first.

Args: symbol: Ticker symbol to short (e.g. "AAPL"). quantity: Number of shares to short. order_type: MARKET, LIMIT, STOP, STOP_LIMIT, MARKET_ON_CLOSE or LIMIT_ON_CLOSE. Default is MARKET. The on-close types execute at the closing auction. time_in_force: DAY or GTD. Default is DAY. limit_price: Required for LIMIT, STOP_LIMIT and LIMIT_ON_CLOSE orders. stop_price: Required for STOP and STOP_LIMIT orders. expiration_time: Required when time_in_force is GTD. ISO 8601 format. equity_market_session: CORE or EXTENDED. account_id: Account ID. Optional if PUBLIC_COM_ACCOUNT_ID is set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "quantity": "<quantity>"
    },
    "name": "place_short_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
quantityYes
account_idNo
order_typeNoMARKET
stop_priceNo
limit_priceNo
time_in_forceNoDAY
expiration_timeNo
equity_market_sessionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true and non-idempotent, but the description adds the crucial operational warning that this executes a real trade and recommends a preflight step. It doesn't disclose retry/duplicate-order risk even though idempotentHint=false, which would be valuable for an agent deciding whether to retry after a timeout.

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?

Purpose and the real-trade warning are front-loaded, followed by a tight Args block where every line supplies information not present elsewhere. No redundant restatement of the tool name or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and all nine parameters are documented despite zero schema coverage. Remaining gap: equity_market_session lists CORE/EXTENDED without explaining the behavioral difference, and there is no note on rejection/partial-fill behavior after submission.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the full load and does: it enumerates allowed values for order_type and time_in_force, states defaults, and specifies the conditional requirements (limit_price for LIMIT/STOP_LIMIT/LIMIT_ON_CLOSE, stop_price for STOP/STOP_LIMIT, expiration_time when GTD). It also adds format details (ISO 8601) and clarifies account_id is optional when PUBLIC_COM_ACCOUNT_ID is set.

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 first sentence names a specific verb and resource ('Place an equity short-sale order'), which cleanly separates it from the sibling place_order and the various preflight_* tools. An agent can pick this tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly directs the agent to run preflight_short_order first, which is a concrete when-to-use hint tied to a real sibling. It doesn't state when-not to use it (e.g. cover/locate failures, account restrictions), so it stops short of full routing guidance.

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