Crank Protocol

strategy_resume

Destructive

Re-enable a paused strategy (manual re-enable after a drawdown pause).

The drawdown kill switch latches a strategy to paused_drawdown and requires this explicit owner action to resume; the equity high-water mark is reset so it does not immediately re-trip.

(spec s7.1): resuming a PERPS-CAPABLE strategy (perp_grid / basis_trade / allow_short / short_only) re-runs the perps jurisdiction gate first -- a wallet whose jurisdiction no longer passes (US / unknown / expired / OFAC / AU) cannot re-engage a paused perps strategy.

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": {
      "strategy_id": "<strategy_id>",
      "wallet_address": "<wallet_address>"
    },
    "name": "strategy_resume"
  }
}

Input Schema

Name	Required	Description	Default
`strategy_id`	Yes
`wallet_address`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing concrete behavior: the equity high-water mark is reset so the strategy does not immediately re-trip, the pause state is 'paused_drawdown', and re-engagement of perps strategies re-runs the jurisdiction gate with specific failure jurisdictions (US/unknown/expired/OFAC/AU). This is exactly the kind of state-change detail annotations alone cannot convey.

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 core action, then layers the drawdown-latch mechanics and the jurisdiction caveat. Information density is high and every clause is useful, though the inline spec reference and parenthetical lists make it slightly dense.

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 destructive, non-idempotent mutation tool with annotations covering the safety profile and an output schema covering return values, the description supplies the missing behavioral and precondition detail. The only real hole is parameter meaning, which leaves it just short of complete.

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

Parameters2/5

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

Schema coverage is 0%, so the description must carry the burden for both parameters. It never explains strategy_id (which strategy to resume) or wallet_address (the owner wallet whose jurisdiction is checked) directly — the wallet's role is only inferable from the jurisdiction-gate sentence. The gap is only partially compensated.

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+resource (re-enable/resume a paused strategy) and immediately scopes it to the drawdown-pause case, cleanly distinguishing it from strategy_pause and strategy_modify. An agent can tell what this 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 Guidelines4/5

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

Gives clear context: this is the explicit owner action required to unlatch a drawdown kill switch, and it explains the perps jurisdiction precondition for re-engagement. It does not name a sibling alternative, but the when-to-use condition is explicit and unambiguous.

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?