Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Snap cuts to the musical beat

beat_align_cuts

Moves internal edit boundaries toward nearby beats within a tolerance while avoiding word interiors. Uses the program's music by default, with options for source audio or an explicitly supplied tempo. The first start and final end remain fixed.

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

Input Schema

NameRequiredDescriptionDefault
bpmNo
sourceNo
every_sNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
tolerance_sNo

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.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the actual mutation scope: only internal boundaries move, the first start and final end stay fixed, and word interiors are protected. It does not address whether a second run shifts cuts further, which matters given idempotentHint=false.

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?

Three short sentences with no filler: what moves first, then how the beat source is chosen, then what is left untouched. The mutation scope is front-loaded, and the immutability caveat closes it cleanly.

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 five-parameter mutation tool with no output schema, the description covers the essential semantics: what changes, what stays fixed, and the default beat source. The remaining gap is the unexplained every_s parameter and no note on what the agent observes after the call.

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 only 20%, so the description must carry weight. It conveys the meaning of tolerance_s, bpm (explicit tempo), and source (music vs. video audio) in prose, but every_s is never mentioned and no units, ranges, or defaults are given for any parameter.

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 states a precise verb and object: it moves internal edit boundaries toward nearby beats, constrained by tolerance and word interiors. That is far more specific than the title alone and distinguishes it semantically from cut_silences or plan_to_music, though it never names a sibling to contrast with.

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 gives useful operating context — defaults to the program's music, with source-audio or explicit-tempo alternatives — but never says when to choose this tool over neighbors such as plan_to_music, suggest_motion_beats, or set_music_fit. Usage is implied by the scenario rather than stated as guidance.

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