AfterLaunch

Cancel unfinished work

withdraw_move

Destructive

Apply your user's explicit decision to cancel (withdraw) unfinished work on an accepted growth move: the job is withdrawn and the move returns to pending. Pass the exact current job and attempt; legacy work also needs the exact move and legacy job states and updated_at. This never publishes anything. Free; requires the 'act' scope.

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": {
      "move_id": "<move_id>",
      "job_id": "<job_id>",
      "expected_attempt_id": "<expected_attempt_id>"
    },
    "name": "withdraw_move"
  }
}

Input Schema

Name	Required	Description
`note`	No
`job_id`	Yes
`move_id`	Yes
`expected_attempt_id`	Yes	Exact current attempt; null for legacy work.
`expected_move_state`	No
`expected_legacy_state`	No	get_move: prepared_result.legacy_state ?? state.
`expected_move_updated_at`	No
`expected_legacy_updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds value on top by stating the state transition (job withdrawn, move back to pending), that nothing is published, that the call is free, and that it requires the 'act' scope. It stops short of saying whether the withdrawn job is recoverable or what happens to the attempt record.

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?

Three tightly packed sentences with the core effect front-loaded before preconditions and constraints. No filler, though the lead-in phrase is slightly ceremonious and the sentences are dense enough that the legacy path is easy to miss.

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 an 8-parameter mutation tool with no output schema, the description covers the effect, the optimistic-concurrency preconditions, the legacy path, cost, and authorization scope. It does not explain what a caller should expect to observe after the call, but with destructive semantics already flagged by annotations the gap is minor.

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 25%, so the description must compensate, and it does: it explains that job and attempt must be the exact current values, and which fields legacy work additionally requires (move and legacy states plus updated_at). Only the optional `note` parameter is left unaddressed.

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 plus the concrete effect: withdrawing a job on an accepted move and returning the move to pending. This distinguishes it implicitly from skip_move/archive_move by outcome, but neither sibling is named, so the agent must reason about which cancellation-style sibling applies.

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?

"Apply your user's explicit decision to cancel" gives a usage cue and the legacy-work sentence implies a second scenario, but there is no explicit when-not guidance and no comparison against the several adjacent siblings (skip_move, archive_move, undo_move, revise_move). Usage is implied rather than directed.

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

All AfterLaunch 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?