Skip to main content
Glama

cancel_render

Stops the active video render started by render, preventing a video file from being made and leaving the project unchanged; safe to call when no render is running.

Instructions

Stop the render that's running (started by render). No video file is made; the project isn't changed. Safe to call when nothing runs. To stop a picture or style job, use picture_status with stop or cancel_style.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_render"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing outcomes: no video file is produced and the project is not modified, which reassures the agent despite destructiveHint=false. It does not say how the cancellation behaves (immediate vs. queued) or what is returned, which keeps it short of a 5.

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 compact sentences: the action and its side effects come first, then the alternative routing. No filler, nothing repeated from the name.

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 zero-parameter action tool with no output schema, this covers purpose, side effects, and alternatives adequately. The only gap is what the agent should expect back after cancelling, which is not stated.

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?

The tool takes zero parameters, so the schema carries the full burden and the description needs no parameter detail; baseline 4 applies.

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 and resource ("Stop the render that's running") and explicitly ties it to the tool that starts it ("started by render"), so an agent can distinguish it from render/render_status without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives both when-to-use (a render is running) and when-not-to-worry ("Safe to call when nothing runs"), and routes the agent to the right alternative for other job types: picture_status with stop, or cancel_style.

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