Crank Protocol

perp_open_short

Destructive

Open a leveraged SHORT perp position on Drift (non-custodial).

Same envelope as perp_open_long, opposite direction. jurisdiction, idempotency_key (optional) and signed_transaction/verify (two-phase execution): see perp_open_long.

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": {
      "wallet_address": "<wallet_address>",
      "market": "<market>",
      "size_usd": "<size_usd>",
      "leverage": "<leverage>"
    },
    "name": "perp_open_short"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	No
`market`	Yes
`verify`	No
`leverage`	Yes
`size_usd`	Yes
`caller_id`	No
`jurisdiction`	No
`pay_in_crank`	No
`payment_header`	No
`wallet_address`	Yes
`idempotency_key`	No
`stop_loss_price`	No
`allow_unverified`	No
`take_profit_price`	No
`signed_transaction`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 12, 2026

addedInput schema / properties / ip

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / jurisdiction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed2 schema fields changedAug 11, 2026

addedInput schema / properties / signed_transaction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / verify

Added value: +{
+  "default": true,
+  "type": "boolean"
+}

First observedJul 27, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations indicate destructiveHint=truehare this is destructive, key for a short opening. The description adds that it is non-custodial and leveraged, but it does not disclose execution risks (e.g., liquidation, slippage, or reversibility). With destructiveHint true, the description should clearly warn about potential losses or irreversible actions, which is missing.

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?

The description is brief and to the point, front-loading the core action and context. It efficiently references a sibling for shared details instead of repeating them, which is a good use of space. The only slight inefficiency is the parenthetical about idempotency_key being optional, which is already in the schema.

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?

With 15 parameters and 0% schema coverage, the description falls short. It does not explain the two-phase execution flow (signed_transaction/verify), stop_loss_price/take_profit_price, or the meaning of ip, caller_id, and other fields. An output schema exists, but the description still lacks critical details for an agent to call it correctly, especially since it is a destructive trading action.

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 0%, so the description must explain parameters. It mentions jurisdiction, idempotency_key, signed_transaction, and verify, but does not define their meaning or syntax beyond referencing perp_open_long. Required params (wallet_address, market, size_usd, leverage) are not described, leaving the agent to infer their purposes from names.

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 clearly states the action: opening a leveraged short perp position on Drift. It references its long counterpart and indicates shared parameters, which helps distinguish it from related tools like short_open. However, it does not explicitly name sibling tools beyond perp_open_long, so it is not fully differentiated from all similar perps.

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 points to perp_open_long for details on jurisdiction, idempotency_key, and two-phase execution, implying similar usage. It does not explicitly state when to use this tool versus alternatives like short_open or perp_close. The guidance is implicit and relies on the sibling description, which is a moderate gap.

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

All Crank Protocol tools Inspect

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

Need Help?