Skip to main content
Glama

HYPERneobroker.com

by com.hyperneobroker.mcp
OverviewDiscussionsAdmin

Place paper order

place_order

Stocks/equities on YOUR validated Alpaca paper account ONLY. No virtual stock book exists. Missing or invalid Alpaca mapping, account-not-ready and broker errors fail explicitly; never a virtual fallback. Args: symbol, qty, side buy|sell, limit_price?, client_order_id?. Returns actual broker order ID/status and confirmed fill data, not an inferred fill. Agent key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyYesQuantity, fractional allowed
sideYes
signalNoOptional signal tag, e.g. 0to100:nyg-win-72 - links the order to a 0to100 competition probability so the leaderboard can rank signal-following P&L
symbolYesTicker - stock (AAPL), crypto (BTC, ETH), gold (GOLD = bullion futures GC=F, virtual fill - not the NYSE ticker), index (SPX, NDX)
dry_runNoPreview only - full validation and live would-be fill price, nothing executed or written
competitionNooptional competition id - scope this call to that competition sub-book
limit_priceNoOptional limit price - sends a LIMIT order instead of market (day). US stocks queue outside 9:30-4 ET and fill at the next open.
client_order_idNoOptional idempotency key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / client_order_id / description
      Previous value: -"Idempotency key, max 64 chars. Reuse on retries; same id within 5 minutes is not re-executed"New value: +"Optional idempotency key"
    • removedInput schema / properties / side / description
      Removed value: -"Trade direction: buy opens/adds shares; sell reduces owned shares"
  2. Changed2 schema fields changed
    • changedInput schema / properties / client_order_id / description
      Previous value: -"Optional idempotency key"New value: +"Idempotency key, max 64 chars. Reuse on retries; same id within 5 minutes is not re-executed"
    • addedInput schema / properties / side / description
      Added value: +"Trade direction: buy opens/adds shares; sell reduces owned shares"
  3. Changed1 schema field changed
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only - full validation and live would-be fill price, nothing executed or written",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker - stock (AAPL), crypto (BTC, ETH), gold (GOLD), index (SPX, NDX)"New value: +"Ticker - stock (AAPL), crypto (BTC, ETH), gold (GOLD = bullion futures GC=F, virtual fill - not the NYSE ticker), index (SPX, NDX)"
  5. Changed1 schema field changed
    • addedInput schema / properties / limit_price
      Added value: +{
+  "description": "Optional limit price - sends a LIMIT order instead of market (day). US stocks queue outside 9:30-4 ET and fill at the next open.",
+  "type": "number"
+}
  6. Changed1 schema field changed
    • addedInput schema / properties / competition
      Added value: +{
+  "description": "optional competition id - scope this call to that competition sub-book",
+  "type": "string"
+}
  7. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world. The description adds real value on top: explicit failure semantics ('mapping/account-not-ready/broker errors fail explicitly; never a virtual fallback'), the guarantee that returned fills are actual broker confirmations rather than inferred, and the 'Agent key required' auth requirement. It stops short of documenting idempotency/repeat-call behavior or rate limits.

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?

Front-loads the critical constraint (real paper account, no virtual fallback) before the arg list, and every clause carries information. Slightly dense and the inline arg enumeration is partly redundant with the schema.

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?

With no output schema, the description correctly explains returns ('actual broker order ID/status and confirmed fill data, not an inferred fill') and covers failure modes and auth. It leaves the three unmentioned optional params (signal, dry_run, competition) to the schema, which is acceptable given high coverage.

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 88%, so the schema already documents 7 of 8 parameters well. The description restates only four args (symbol, qty, side, limit_price?, client_order_id?) and omits signal, dry_run and competition, adding no syntax or format meaning beyond the schema. Baseline 3 applies when schema does the heavy lifting.

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?

States a specific verb (place order) and resource (stocks/equities on the validated Alpaca paper account), and implicitly separates itself from sibling tools such as place_fx_order, place_perp_order and place_prediction_order by naming the instrument class. An agent can tell what it does 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 Guidelines3/5

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

The description establishes the environment ('YOUR validated Alpaca paper account ONLY', 'no virtual stock book exists') which implies when the tool is valid, but never states explicit when-to-use/when-not conditions or names an alternative for other instrument classes. Usage is implied rather than spelled out.

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

All HYPERneobroker.com toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources