Skip to main content
Glama

Cancel a Playground creative run

playground_run_cancel
DestructiveIdempotent

Stop further agent effects for a run. Provider jobs already submitted may continue and retain their receipts and charges.

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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "playground_run_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID returned by preparation or execution for this project.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes
queuedJobsCancelledYes
submittedJobsContinueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: cancellation only stops further agent effects, and already-submitted provider jobs may continue and retain their receipts and charges — a cost/side-effect nuance the annotations cannot express.

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?

Two tight sentences: the action is stated first, then the important caveat about residual provider jobs and charges. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be explained, and parameters are fully covered by the schema. Combined with annotations, the description gives enough for correct invocation; only an explicit pointer to sibling operations is missing.

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 100%, with both runId and projectId fully documented including UUID format and provenance. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

Uses a specific verb+resource combination: 'Stop further agent effects for a run', which an agent can map directly to cancelling a Playground run. It is clear about scope (agent effects only), though it does not name a sibling like playground_run_steer or playground_run_revert to sharpen the distinction.

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?

Usage is implied rather than stated: an agent infers it should call this to halt a run, and the second sentence usefully clarifies that in-flight provider jobs are not stopped. There is no explicit when-to-use vs when-not guidance and no named alternative such as steering or reverting a run instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.