Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Set fades

set_fades
Idempotent

Sets opening and closing fades for picture and audio. Durations are in seconds; zero clears the corresponding fade.

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": {
      "project_id": "<project_id>"
    },
    "name": "set_fades"
  }
}

Input Schema

NameRequiredDescriptionDefault
fade_in_sNo
fade_out_sNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral value by explaining that 'zero clears the corresponding fade' and that durations are in seconds. It does not disclose whether the fades apply to the whole project, a selected range, or a specific clip, nor whether existing fades are overwritten.

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 tight clauses: the first declares what is affected, the second gives the unit and the clearing convention. Front-loaded and free of filler.

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 simple three-parameter, no-output-schema tool with a documented required key and covered units/sentinel semantics, the definition is close to sufficient. The notable remaining gap is scope of application (project vs. range vs. clip), which an agent would want to know before calling.

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 only 33% (%s fields for fade_in_s and fade_out_s are bare), so the description must compensate for two of three parameters — and it does, giving the unit (seconds) and the sentinel value (zero clears). Only project_id is documented in the schema itself, and the description does not restate or extend that.

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 (sets) and resource (opening/closing fades) and scopes it to both picture and audio, which tells an agent exactly what changes. It does not distinguish itself from neighboring tools like set_transitions, set_audio_gain, or set_volume, so the agent must infer whether a fade-in is better done here or via a gain ramp.

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: an agent can infer this is the tool for adding or removing head/tail fades. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as set_transitions for crossfades or set_audio_gain for level ramps.

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

All Valmera — AI Video Editor 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