Skip to main content
Glama

Stop a render

render_cancel
DestructiveIdempotent

Stop a render. Pictures already made stay saved.

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": {
      "job": "<job>"
    },
    "name": "render_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesId from render.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job / description
      Previous value: -"The id render returned."New value: +"Id from render."
  2. Added

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, so the key added value is the reassurance that already-produced pictures remain saved — this clarifies the real blast radius of a "destructive" call. It does not say what happens to partially written frames or whether the stopped job can be resumed, but it meaningfully qualifies the destructive annotation rather than contradicting it.

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 short sentences, action stated first, caveat second. 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?

For a single-parameter stop action with full annotation coverage and no output schema, purpose plus the persistence caveat is essentially enough to invoke it correctly. Only the fate of in-progress output is left unstated.

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 100% and there is only one parameter, whose description ("Id from render.") points at the render tool. The description text adds nothing further about the job identifier, so the baseline 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?

"Stop a render" gives a specific verb and resource, so the agent knows this terminates an in-progress render. It does not differentiate against near-siblings like cancel_job or render_frames, but the resource named is distinct enough to act on.

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 only implied: the agent can infer this is for halting a render that is still running. There is no explicit when-not guidance (e.g. what to do with a finished render) and no named alternative for cancelling other job types.

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.

Resources