Skip to main content
Glama

Cancel a queued documentary and refund held credits

cancel_documentary_film
DestructiveIdempotent

Cancel a queued documentary before rendering begins and release its held credits back to the account.

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": {
      "film_id": "<film_id>"
    },
    "name": "cancel_documentary_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
film_idYesQueued film ID to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds important behavior beyond them: the film must still be queued, rendering must not have begun, and held credits are released back to the account.

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?

It is a single, front-loaded sentence with no redundant or filler wording. The cancellation action, eligibility condition, and refund effect are all packed into one clear statement.

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 simple one-parameter mutation with annotations covering destructive and idempotent behavior, the description supplies the essential pre-rendering constraint and credit-release outcome. It could mention behavior when the film is no longer queued, but no major gap remains for correct invocation.

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%, so the single film_id parameter is already documented. The description reinforces that the ID refers to a queued film but adds no new meaning about format, constraints, or lookup behavior beyond the schema.

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?

The description states a specific verb and resource ('Cancel a queued documentary') and adds the scoping condition 'before rendering begins,' which clearly distinguishes it from creation, retrieval, and credit-checking siblings.

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?

It gives a clear when-to-use condition: only for queued films and only before rendering starts. It does not explicitly describe when not to use it or name an alternative for already-rendering films, so it falls short of full routing guidance.

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.