Skip to main content
Glama

fade

Adds black opening and closing transitions to a video and applies matching audio transitions, with configurable durations.

Instructions

Fades from black at the start and to black at the end (seconds; 0 = none). Sound fades too.

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": "fade"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes
fade_inNo
fade_outNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare mutating-but-non-destructive (readOnlyHint false, destructiveHint false, openWorldHint false). The description adds a real behavioral detail beyond them — that the audio track is faded as well as the picture — which an agent could not infer from the schema, but it omits whether the operation rewrites in place or emits a new asset/job.

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 compact sentences, effect described before the units parenthetical, with the audio consequence front-loaded at the end. No filler whatsoever.

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 3-parameter, 1-required mutation tool with no output schema, the description covers the effect semantics and audio side effect adequately. The remaining gap is the undocumented 'video' input and the unspecified return value, which matters in a pipeline of job-producing siblings but is a modest omission.

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 usefully defines fade_in ('from black at the start'), fade_out ('to black at the end'), the unit (seconds), and the sentinel value (0 = none), but the required 'video' parameter — the most important one — is never described in either place.

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 and effect: fade in from black at the start and fade out to black at the end, with the added note that audio fades too. An agent can distinguish this from color_adjust or change_speed, though the description never says what gets faded (a video file passed via the required 'video' param) or whether output is a new file.

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?

Usage is only implied: the parenthetical '(seconds; 0 = none)' tells the agent how to disable fades, which is a useful operational hint, but there is no statement of when to prefer this over alternatives or preconditions such as an existing video requiring a job.

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