Skip to main content
Glama

HYPERneobroker.com

by com.hyperneobroker.mcp
OverviewDiscussionsAdmin

Place paper order

place_order

Place a paper trade on YOUR OWN agent account - virtual book, simulated money, fills at live feed prices. Args: symbol (AAPL, BTC, ETH, GOLD, SPX...), qty (fractional ok), side buy|sell, optional client_order_id (5-min dedupe). Requires a free agent key (POST /register, zero human steps). Paper desks: $1,000,000 paper cash to start (Alpaca-backed accounts top up $50k/day to $1M; virtual lanes start at the full $1M). No desk guards: any order size, any position count, any pace - the $1M paper pool is the only ceiling. Desk calls: no daily cap, unmetered.

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

A4/5.0
Behavior5/5

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

Annotations only cover safety hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false), while the description adds the things an agent actually needs: fills occur at live feed prices, client_order_id provides a 5-minute dedupe window, no desk guards on size/position/pace, no daily cap, and the paper cash top-up behaviour. That is substantive disclosure well beyond the structured fields and is consistent with them.

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-loaded with the core action and the account constraint, then argument list, then economics. Dense and mostly waste-free, though the shouting caps ('YOUR OWN') and the marketing-style capitalisation add noise without information.

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 8 parameters, no output schema, and four annotations, the description covers the essential context: authentication path, pricing model, capacity limits, and idempotency. It omits failure modes (insufficient paper cash, rejected symbols) and any hint at the response shape, which are the only real gaps.

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

Parameters4/5

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

Schema description coverage is already 88%, so the baseline is 3, but the description adds meaning the schema lacks: the 5-minute dedupe window for client_order_id, confirmation that qty accepts fractions, and the GOLD = GC=F virtual-fill caveat. It leaves limit_price and dry_run semantics entirely to the schema.

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?

States a specific verb and resource ('Place a paper trade on YOUR OWN agent account') and pins the modality (virtual book, simulated money, live feed fills). It does not, however, differentiate itself from the closely named siblings place_perp_order, place_prediction_order and place_sports_bet, so an agent still has to infer that this is the generic spot paper-order entry point.

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?

Gives a prerequisite ('Requires a free agent key (POST /register)') and operational framing (no daily cap, unmetered, $1M paper pool), but never says when to choose this over the sibling order-placement tools. Usage is implied rather than stated.

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