Skip to main content
Glama

video_transform_get

Read video window-fit settings—aspect override, rotation, zoom, pan-scan, and deinterlace—to understand how the picture is framed during playback.

Instructions

Read how the picture is fitted to the window: aspect override, rotation, zoom multiplier, pan-scan and deinterlace. Distinct from filter_list, which is colour rather than geometry.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does signal read-only semantics via 'Read' plus the enumeration of retrievable fields. It does not discuss failure modes (e.g., when no transform is configured) or permissions, but for a zero-parameter read this is reasonable coverage.

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 sentences, front-loaded with the action and the subject, zero filler. The sibling disambiguation is compressed into a single clause and still parses cleanly.

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?

No output schema exists, and the description compensates by listing the setting categories returned, which is what an agent needs to decide whether this tool answers its question. Missing only edge detail on absent/unset settings.

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?

There are zero parameters, so the baseline is 4. The description adds useful meaning by naming the five setting groups a caller gets back, which goes beyond any schema surface (the input schema is empty).

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 ('Read') and a concrete subject ('how the picture is fitted to the window'), then enumerates the exact settings covered (aspect override, rotation, zoom, pan-scan, deinterlace). It explicitly separates itself from filter_list on colour vs geometry grounds, making selection unambiguous without opening a schema.

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 when to call it (inspecting geometry/fit settings rather than colour filters) and names the sibling it is not. It does not explicitly point at video_transform_set for making changes or video_transform_reset for reverting, but those names plus the read framing carry the intent.

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