Skip to main content
Glama

color_adjust

Adjust a video's brightness, contrast, saturation, and warmth to correct exposure, balance color, or apply a stylized look before export.

Instructions

brightness -1..1 (0 = same), contrast 0.5..2 (1 = same), saturation 0..3 (1 = same), warmth -1 cool .. 1 warm.

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": {
      "video": "<video>"
    },
    "name": "color_adjust"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes
warmthNo
contrastNo
brightnessNo
saturationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond parameter ranges: it does not say whether the original video is modified or preserved, what happens to unspecified settings, or what the operation returns.

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?

The description is a single compact fragment with no filler, and every listed range carries useful information. Its terseness is appropriate, though it is not structured as a complete statement of purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with five parameters, 0% schema description coverage, and no output schema, the description is too sparse. It provides only color parameter ranges while omitting the action, the required video input semantics, and the outcome of applying the adjustment.

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 description adds useful meaning beyond the schema by giving ranges and neutral values for four of the five parameters, which the schema does not provide. It fails to document the required video parameter, so it does not fully compensate for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates adjustment ranges for brightness, contrast, saturation, and warmth, so the broad purpose is inferable from the name and parameters. However, it never states that this tool adjusts video color or what resource it operates on, leaving the action and target implicit rather than explicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no comparison with sibling tools such as auto_fix or fade. The description is purely a parameter range reference and provides no workflow context.

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