Skip to main content
Glama

Outil.io

Set video transform

set_video_transform
Destructive

Position, échelle et opacité statiques. x/y sont des coordonnées normalisées du centre ; 0,5/0,5 centre l’image. Refuse une animation existante : utiliser les outils keyframes. Exige la version actuelle du montage ; renvoie la nouvelle version.

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": {
      "projectId": "<projectId>",
      "version": "<version>",
      "clipId": "<clipId>",
      "transform": "<transform>"
    },
    "name": "set_video_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
versionYes
projectIdYes
transformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), it discloses three useful behaviors: the transform is static only, the call fails if an animation already exists, and it is version-guarded (requires current version, returns the new version) — an optimistic-concurrency contract the schema does not convey. It does not say what happens to previously set transform values or how the failure on animation surfaces, so it stops short of a 5.

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?

Three short sentences, zero filler, and the most decision-relevant constraint (static-only, use keyframes for animation) is front-loaded right after the scope statement. Every clause carries information the agent cannot get from the schema or annotations.

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 4-required-parameter mutation with a nested transform object and no output schema, the definition covers the version contract, the return of a new version, and the animation conflict. The remaining gap is the value semantics/domains of scale, opacity and clipId, which leaves it just short of complete.

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 description coverage is 0%, so the description must carry the load. It does well for x/y — normalized center coordinates, 0.5/0.5 centers the image — and explains the version parameter's role. But it says nothing about scale (0.05–3), opacity (0–1), or clipId, leaving half the parameters' meaning entirely to the bare 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 names the exact resource attributes it mutates (static position, scale, opacity) and adds an essential qualifier: 'statiques' as opposed to animated. It stops short of an explicit verb ('sets'), relying on the title 'Set video transform' and the tool name for the action, but an agent can still tell this apart from the keyframe tools it is explicitly contrasted with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states an explicit negative condition — 'Refuse une animation existante : utiliser les outils keyframes' — which routes the agent to a different family of tools when an animation is present. It also states the precondition that the current montage version is required, which is a when-to-use rule for the version parameter.

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.