Skip to main content
Glama

Outil.io

Set video chroma key

set_video_chroma_key
Destructive

Supprimer un fond uni par couleur #RRGGBB, tolérance similarity et adoucissement blend. null désactive. Ne fait pas de détourage sémantique sur décor complexe. 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>",
      "chroma": "<chroma>"
    },
    "name": "set_video_chroma_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
chromaYes
clipIdYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive=true and readOnly=false, and the description adds real context beyond them: it requires the current project version (optimistic concurrency), returns the new version, and null is a destructive reset. It does not say what happens on a version mismatch, which is the main remaining gap for a destructive mutation.

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?

Four short sentences, front-loaded with the core action, then constraints, then the version contract. No filler and nothing repeated 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 destructive single-clip mutation with no output schema, the description covers the effect, the disable path, the limitation, and the version contract. Only the failure behaviour on a stale version is unaddressed.

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 carries the burden. It explains chroma.color format (#RRGGBB), similarity as tolerance, blend as softening, and null as disable, but says nothing about clipId or projectId semantics, and version is only mentioned as a requirement, not explained as a parameter.

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 action (remove a solid background by #RRGGBB color) with named controls (similarity, blend) and a disabler (null). It also carves out what it is not ('ne fait pas de détourage sémantique'), implicitly separating it from semantic masking siblings, though it never names the alternative tool.

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 a clear usage envelope: works on uniform backgrounds, explicitly not for complex scenery, and null disables the effect (the undo path). Missing an explicit pointer to which sibling to use for semantic matting, so the routing decision is left half-inferred.

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.