Skip to main content
Glama

platform_cancel_pending

Cancels a pending platform run by pending ID, preventing queued work from starting. Returns an explanation for terminal or unknown IDs instead of cancelling.

Instructions

Cancel a pending platform run (pending_runs row). CAS: only rows still pending/claimed can be cancelled; terminal rows return an explanation, unknown ids {"status": "not_found"}.

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": {
      "pending_id": "<pending_id>"
    },
    "name": "platform_cancel_pending"
  }
}

Input Schema

NameRequiredDescriptionDefault
pending_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the compare-and-set guard, that terminal rows produce an explanation instead of a cancellation, and the exact not_found payload for unknown ids. These are concrete failure-mode behaviors an agent cannot get from the annotations. The cancel operation is a state mutation while destructiveHint=false, but that is a scoping choice rather than a contradiction.

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?

Two tight sentences that front-load the action and then the constraint. The CAS shorthand assumes familiarity but wastes no words.

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?

With an output schema covering the return values, a single parameter, and annotations covering the safety profile, the description supplies the remaining needed context: eligibility and failure modes. Only the pending_id semantics remain thin.

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 coverage is 0% for the single pending_id integer parameter, so the description must carry the load. It references 'ids' and describes the not_found response for unknown ones, which implies the parameter identifies a pending_runs row, but it never states the type or the expected id source, leaving a gap.

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: cancel a pending platform run, and clarifies the underlying object as a pending_runs row. This implicitly separates it from sibling platform_cancel_run (non-pending runs), but the sibling is never named, so the differentiation is left to inference.

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 CAS note conveys the precondition: only rows still pending/claimed are eligible, and terminal rows will not be cancelled. That is implied usage guidance rather than explicit when-to-use/when-not guidance, and no alternative tool is named for other run states.

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