Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Conceal jump cuts

conceal_jump_cuts

Reports same-shot jump cuts and their existing visual coverage without modifying the edit in report mode. The scale-step mode can apply hard, nonanimated framing steps to selected jumps.

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

Input Schema

NameRequiredDescriptionDefault
atNo
modeNo
stepNo
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. Changed1 schema field changed
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "scale_step",
-  "off"
-]New value: +[
+  "report",
+  "scale_step",
+  "off"
+]
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false and destructiveHint=false, and the description usefully adds that report mode leaves the edit untouched while scale-step applies "hard, nonanimated" framing — real behavioural context. It still omits how jumps are selected for modification, what the "off" mode does, and whether applied steps are reversible or re-runnable (idempotentHint is false but unaddressed).

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 written sentences, with the non-mutating behaviour front-loaded before the mutating mode. Nothing is redundant, though the second sentence's "can apply" phrasing is slightly hedged for a mode that performs the actual edit.

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?

This is a mode-switched tool that can both inspect and mutate a timeline, with no output schema and 75% of its parameters undocumented. The description explains the mode split but leaves the selection input, the step magnitude, and the report's contents unexplained — not enough for an agent to invoke scale-step confidently.

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?

Schema coverage is only 25%, with just project_id documented, so the description must carry the other three parameters. It names the report and scale-step modes but never explains "off", never says what the `at` array denotes (positions? timestamps? jump indices?), and gives no units, defaults, or bounds for `step`.

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 names a specific verb and resource ("Reports same-shot jump cuts and their existing visual coverage") and distinguishes two operating modes, report and scale-step. An agent can tell this apart from neighbours like find_shots or suggest_match_cuts, though it never names those alternatives 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?

It implies when each mode applies: report mode for inspection without touching the edit, scale-step mode when the agent wants to actually apply framing steps. There is no explicit when-not guidance, no prerequisites, and no routing advice versus siblings such as punch_in_on_emphasis or add_zoom, so the selection logic is only partially inferable.

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