Revid

Cancel episode

cancel_episode

DestructiveIdempotent

Stop a Series Maker run from create_episode: the step in progress finishes (what it generates is charged), nothing after it starts. Requires an active Revid plan.

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

Input Schema

Name	Required	Description	Default
`runId`	Yes	The runId returned by `create_episode`.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`method`	Yes
`status`	Yes
`endpoint`	Yes
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well past the annotations by explaining exactly what happens on cancel: the in-progress step finishes, its generated output is still charged, and nothing after it starts. That cost and partial-completion semantics are precisely the information `destructiveHint` cannot convey.

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 with the cancellation semantics front-loaded and the plan prerequisite placed last; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive cancel tool with an output schema and full annotation coverage, the description supplies everything an agent needs: trigger, blast radius, billing consequence, and precondition.

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?

The single `runId` parameter is fully documented in the schema, including that it comes from `create_episode`. The description adds no format, source, or validation detail beyond what the schema already states, so the baseline 3 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?

Specific verb and resource ("Stop a Series Maker run") tied back to the creator tool `create_episode`, which immediately distinguishes it from siblings like `get_episode_status` or `create_episode`.

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

Usage Guidelines4/5

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

Gives clear context for use (cancelling an in-flight Series Maker run) and a stated prerequisite ("Requires an active Revid plan"), but does not explicitly route an agent that only wants to check progress toward `get_episode_status` instead.

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

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