Skip to main content
Glama

HYPERneobroker.com

by com.hyperneobroker.mcp
OverviewDiscussionsAdmin

Place perp paper order

place_perp_order

Paper-trade perpetual futures on YOUR agent book: {coin (BTC, ETH, SOL, xyz:NVDA...), qty, side buy|sell}. Fills at the live Hyperliquid / trade.xyz mark. Same book, cash and guards as place_order. Agent key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyYes
coinYes
sideYes
signalNoOptional signal tag for leaderboard ranking
dry_runNoPreview only - full validation and live would-be fill, nothing executed or written
competitionNooptional competition id - scope this call to that competition sub-book
client_order_idNoOptional idempotency key (5-min dedupe)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / coin / description
      Removed value: -"Perpetual instrument, e.g. BTC, ETH, SOL, or xyz:NVDA"
    • removedInput schema / properties / qty / description
      Removed value: -"Positive quantity in contracts/base-asset units, e.g. 0.01 BTC"
    • removedInput schema / properties / side / description
      Removed value: -"Trade direction: buy opens/adds long; sell opens/adds short or reduces long"
  2. Changed3 schema fields changed
    • addedInput schema / properties / coin / description
      Added value: +"Perpetual instrument, e.g. BTC, ETH, SOL, or xyz:NVDA"
    • addedInput schema / properties / qty / description
      Added value: +"Positive quantity in contracts/base-asset units, e.g. 0.01 BTC"
    • addedInput schema / properties / side / description
      Added value: +"Trade direction: buy opens/adds long; sell opens/adds short or reduces long"
  3. Changed2 schema fields changed
    • addedInput schema / properties / client_order_id
      Added value: +{
+  "description": "Optional idempotency key (5-min dedupe)",
+  "type": "string"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only - full validation and live would-be fill, nothing executed or written",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / competition
      Added value: +{
+  "description": "optional competition id - scope this call to that competition sub-book",
+  "type": "string"
+}
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations mark this as a non-readonly write, and the description adds real context beyond them: it is paper-traded (no real capital), fills at the live Hyperliquid / trade.xyz mark, shares the same book/cash/guards as place_order, and requires an agent key. It omits return/response behavior, but the pricing and auth disclosures are valuable.

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?

A single front-loaded sentence block: purpose and instrument first, then parameter shape, then fill source, book semantics and auth. Dense but no filler; the set-notation for parameters is compact.

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?

For a 7-param mutation tool with no output schema, the description covers purpose, fill source, shared-book semantics and the agent-key requirement. It could say more about fill result handling and the dry_run/competition interplay, but nothing essential for correct invocation is missing.

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 coverage is only 57% and the required coin/qty/side fields are undocumented in the schema, so the description compensates by spelling out coin with concrete examples (BTC, ETH, SOL, xyz:NVDA) and the side enum. The optional params already carry schema descriptions, so the added value centers correctly on the required ones.

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 (paper-trade) and resource (perpetual futures on YOUR agent book), and gives the required parameter shape with coin examples and the buy|sell sides. It references the sibling place_order to signal it is the perp variant of that tool, though it never states the spot-vs-perp distinction explicitly.

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?

Saying 'Same book, cash and guards as place_order' implies relationship to a sibling, and 'Paper-trade' signals the simulation context, so usage is inferable. However there is no explicit when-to-use / when-not-to-use, and no direct comparison telling the agent when to pick place_perp_order over place_order or place_prediction_order.

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