Crank Protocol

strategy_perp_grid_create

Destructive

Create a perp-grid strategy -- a ladder of perp LONGS accumulated on dips.

Routes through the multi-venue perps VENUE ADAPTER (hard rule 2; Jupiter Perps primary). Around a rolling center price (SMA, or an explicit center_price), each grid_spacing_pct move below center is one rung; crossing a deeper rung opens a perp long sized usd_per_level at leverage. PAUSES new rungs in a trending (bull/bear) regime and closes the ladder in a bear (stop the bleed); tightens spacing in range, widens when volatile. Only an asset with a mapped perp market (currently SOL) can open -- see get_venue_status for routable markets. venue optional (defaults to the configured primary); a Tier B (custodied) venue needs acknowledge_tier_b=true after reviewing its custody_disclosure.

risk: see strategy_dca_create.

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>",
      "target_token": "<target_token>",
      "usd_per_level": "<usd_per_level>"
    },
    "name": "strategy_perp_grid_create"
  }
}

Input Schema

Name	Required	Description	Default
`risk`	No
`venue`	No
`leverage`	No
`grid_levels`	No
`center_price`	No
`slippage_bps`	No
`target_token`	Yes
`center_period`	No
`range_tighten`	No
`usd_per_level`	Yes
`volatile_widen`	No
`wallet_address`	Yes
`grid_spacing_pct`	No
`interval_seconds`	No
`acknowledge_tier_b`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate destructive and open-world behavior, but the description goes further: it discloses that the strategy pauses new rungs in trending regimes, closes the ladder in a bear, tightens/widens spacing based on volatility, and requires acknowledge_tier_b for Tier B venues. This explains the destructive impact beyond the annotations.

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?

The description is about 100 words, front-loaded with the core purpose, and every sentence adds value: mechanics, regime behavior, venue constraints, and risk reference. It is dense yet well-structured, with no 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?

For a complex 15-parameter tool with output schema, the description covers the primary behavior, venue routing, asset restrictions, and risk acknowledgment. It leaves a few parameters unexplained but provides enough context for an agent to use the tool correctly and know where to look for additional details.

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?

With 0% schema coverage, the description adds meaning for several key parameters: grid_spacing_pct, center_price, usd_per_level, leverage, venue, acknowledge_tier_b, range_tighten, and volatile_widen. It also refers to strategy_dca_create for the risk parameter. Some parameters like center_period, grid_levels, slippage_bps, and interval_seconds remain unexplained, preventing a perfect score.

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 description opens with 'Create a perp-grid strategy -- a ladder of perp LONGS accumulated on dips,' which gives a specific verb and resource. It then explains the mechanism (rungs below center price, perp long sizing) making it clearly distinct from sibling strategy tools like DCA or market making.

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?

The description implies when to use the tool (for accumulating longs on dips) and provides constraints (only assets with a mapped perp market, see get_venue_status). It does not explicitly state when not to use it or directly contrast with alternative strategies, though the mechanism and venue caveats give clear context.

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?