Skip to main content
Glama

video_transform_reset

Restores a video's original geometry by removing aspect overrides, rotation, zoom, pan-scan, and deinterlace settings, returning playback to its native unmodified view.

Instructions

Restore the file's own geometry — no aspect override, no rotation, no zoom or pan-scan, deinterlace off.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on the resulting state — spelling out that aspect override, rotation, zoom/pan-scan, and deinterlace are all turned off — but says nothing about whether this mutates the underlying file or just the session preview, whether it persists, or whether the reset is reversible.

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?

A single front-loaded sentence with zero waste; the em-dash enumeration communicates the full reset scope more compactly than prose would.

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 reset with no output schema and no annotations, the description covers what changes and what the end state is. The only meaningful gap is persistence/scope (file vs. preview, undoability), which keeps it short of full completeness.

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 there is no parameter meaning to add; the baseline of 4 applies. The description correctly focuses its words on scope of effect rather than inventing argument detail.

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?

States a specific verb ("Restore") and a specific resource ("the file's own geometry"), then enumerates exactly which transform categories are cleared. An agent can distinguish this from video_transform_set/get by the word "reset" and the enumeration of cleared state, though it never names its siblings explicitly.

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: an agent can infer this is the undo/cancel path for prior transforms, but the description never says when to prefer it over video_transform_set, nor any preconditions (e.g., whether transforms must currently be active). No exclusions or alternatives are stated.

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

Deploy Server

Other Tools