Skip to main content
Glama

retry film protection change

retry_film_protection_change

Retry a failed protection change only while Studio allows it. This cannot retry an admin-only encoding job.

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": "retry_film_protection_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
film_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a non-readonly, non-idempotent, non-destructive, closed-world operation. The description adds that it applies to failed protection changes, is gated by Studio availability, and excludes admin-only encoding jobs, but it does not explain permissions, side effects, or what happens when the retry fails.

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?

The definition is two short, front-loaded sentences with no filler. The purpose and key exclusions appear immediately, even though the term 'Studio' is left undefined.

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

Completeness3/5

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

For a single-parameter mutation with annotations but no output schema, the description covers the core action and a notable exclusion. It remains incomplete because 'Studio allows it' is undefined and there is no guidance on error handling, prerequisites, or relation to set/cancel protection tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never mentions film_id or explains which film's protection change is being retried. The property name and UUID format make the parameter inferable, but the description adds no meaning beyond the schema.

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?

The description uses a specific verb and resource: retrying a failed protection change. It also scopes the operation away from an admin-only encoding job, though it does not name sibling alternatives such as set_film_protection or cancel_film_protection_change.

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?

It gives a limited precondition ('only while Studio allows it') and an exclusion ('cannot retry an admin-only encoding job'). However, 'Studio allows it' is not actionable and the description does not direct the agent to an alternative when retry is unavailable.

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