Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Cut a range of the finished edit

cut_output_range

Removes one interval on the assembled program clock, including intervals that cross inserted clips. Affected source ranges and inserts are split or removed as appropriate, with dependent timing re-anchored in one versioned write.

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

Input Schema

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

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

Annotations only declare mutability flags; the description adds real behavior beyond them: intervals spanning inserted clips are handled, affected source ranges and inserts are 'split or removed as appropriate,' and the whole change lands in 'one versioned write.' The versioned-write wording is consistent with the non-destructive framing, though recoverability/undo is only hinted at.

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 tightly written sentences with the core action and scope front-loaded, followed by the splitting/re-anchoring consequence. No filler and no restatement of the title.

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 single-interval mutation with no output schema, the description covers the key semantics: coordinate space, cross-clip behavior, splitting, and atomicity. Gaps around units/optionality of start and end keep it short of full completeness.

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 coverage is low (33%) and start/end have no schema descriptions, but the description does clarify that the interval sits on the assembled program clock rather than source time, which is meaningful disambiguation. It still says nothing about units, inclusivity of endpoints, or why start/end are optional when only project_id is required.

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 target: 'Removes one interval on the assembled program clock.' The phrase 'assembled program clock' implicitly separates it from source-level siblings like cut_range, but no sibling is named and the distinction from keep_segments/restore_range is left to inference.

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 by the phrase 'assembled program clock' and the fact that it handles cross-clip intervals. There is no explicit statement of when to use this instead of cut_range, cut_silences, keep_segments, or restore_range, and no prerequisite or exclusion 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