Valmera — AI Video Editor

Set speed ramp

set_speed_ramp

Idempotent

Adds an eased speed ramp within one shot or across an identified video insert. Source frame rate constrains duplicate-free slow motion; explicit options govern duplicate frames and speech-bearing windows.

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_speed_ramp"
  }
}

Input Schema

Name	Required	Description
`id`	No
`end`	No
`low`	No
`hold`	No
`curve`	No
`start`	No
`insert`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`allow_speech`	No
`allow_duplicates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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."

AddedOct 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare the safety profile (non-read-only, idempotent, non-destructive, closed-world), so the description doesn't need to repeat it. It adds genuine domain behavior instead: source frame rate limits duplicate-free slow motion, and duplicate frames and speech-bearing windows are governed by explicit options. It still omits what happens when constraints are violated and how the ramp interacts with existing speed effects.

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?

Two tightly packed sentences with no filler, and the core action is front-loaded. The second sentence is dense to the point of being slightly opaque ('explicit options govern...'), but nothing is redundant.

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

Completeness3/5

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

For a 10-parameter mutation tool with no output schema and near-zero schema descriptions, the definition covers purpose and some domain constraints but leaves most parameter meaning and result behavior to inference. It is adequate to recognize the tool, not fully adequate to invoke it confidently across the many optional parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 10% schema description coverage, the description carries most of the documentation burden, yet it only gestures at a few: 'duplicate frames' maps to allow_duplicates, 'speech-bearing windows' to allow_speech, and frame-rate constraints hint at the speed range. The roles of start, end, hold, curve, id versus insert, and how they interact are left entirely undocumented in both schema and description.

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 uses a specific verb and resource ('Adds an eased speed ramp') and states the two scopes it can apply to ('within one shot or across an identified video insert'). That scope language implicitly distinguishes it from plain set_speed and remove_speed, though it never names those siblings directly.

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 implied by the scope clause: an agent can infer this is the tool for gradual eased speed changes rather than uniform retiming, and that it can target either a shot id or an insert. However there is no explicit 'use this instead of set_speed when...' routing, no prerequisites, and no stated failure conditions.

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 tools Inspect

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.