Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Video Reframe

video_reframe
Destructive

Crops a video to a target aspect ratio (e.g. "9:16" vertical, "1:1" square, "4:5") around a focus point — for social clips. Takes the LARGEST crop of that aspect that fits, centered on focus (x,y in source pixels, top-left origin; default = center) and clamped to the frame. Audio passes through. Returns the output path + new dimensions.

Input Schema

NameRequiredDescriptionDefault
focusNo{x,y} center of interest in source pixels (top-left). Default: frame center.
inputYesPath to the source video file.
aspectYesTarget aspect "W:H", e.g. 9:16, 1:1, 4:5, 16:9.
outputNoDefault: <input>_<aspect>.mov. Missing parent folders are created.
confirmNoIgnored; kept for older clients.
overwriteNoReplace an existing file at output. Without it an existing output is refused. The input is never overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to write the output. Without it the call returns a preview and writes nothing."New value: +"Ignored; kept for older clients."
  2. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to write the output. Without it the call returns a preview and writes nothing.",
+  "type": "boolean"
+}
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Replace an existing file at output. Without it an existing output is refused. The input is never overwritten.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / output / description
      Previous value: -"Default: <input>_<aspect>.mov"New value: +"Default: <input>_<aspect>.mov. Missing parent folders are created."
  4. Changed1 schema field changed
    • addedInput schema / properties / input / description
      Added value: +"Path to the source video file."
  5. Added

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the crop algorithm ('takes the LARGEST crop that fits'), the clamping behavior, audio passthrough, and the key safety fact that 'The input is never overwritten' — which scopes the destructiveHint=true to the output file only. It could still say more about output collision handling, but the schema covers the overwrite flag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and target, then behavior, then return value — every sentence carries information. Minor redundancy in restating the focus x,y top-left convention already in the schema.

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?

With 6 parameters, nested focus object, no output schema, and destructive annotations, the description covers what an agent needs: crop logic, focus default, audio handling, overwrite safety, and return value ('output path + new dimensions'). Nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds value by specifying that focus is the crop center, that it is clamped to the frame, and that the crop maximizes area for the given aspect. The x,y/top-left/default-center detail duplicates the schema, so not a 5.

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?

Opens with a specific verb+resource ('Crops a video') plus the target ('target aspect ratio') with concrete examples (9:16, 1:1, 4:5). This clearly separates it from sibling video tools like video_trim, video_concat, and video_blur_region.

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?

The phrase 'for social clips' implies the intended use case, but there is no explicit when-to-use rule, no exclusions, and no mention of when to pick this over video_trim or video_blur_region. Usage is inferable but not guided.

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

All Local MCP toolsInspect
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