Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Make variant set

make_variant_set

Creates up to six registered, procedurally transformed still-image variants from one main-video frame at a program timestamp. Saves the images as project assets without placing them in the edit.

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

Input Schema

NameRequiredDescriptionDefault
tYesprogram s
kindsNo
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. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not idempotent, not destructive, closed world); the description adds real behavioral context by stating that images are persisted as project assets and deliberately not placed in the edit. That side-effect disclosure is valuable. It still omits what happens on repeated calls (relevant given idempotentHint=false) and whether existing assets are overwritten or duplicated.

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 sentences with the operation front-loaded and the persistence-does-not-touch-the-edit constraint immediately after. No filler, no restatement of the title.

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 mutating, non-idempotent tool with no output schema, the description covers where results land but not what is returned (asset identifiers) or what the accepted kinds are, leaving real gaps. The annotations cover safety, so the deficit is moderate rather than severe.

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?

The description clarifies that 't' is a program timestamp, which compensates for the truncated schema text 'program s'. However, the 'kinds' array has no description in the schema and none in the description, so the agent does not know which variant kinds are valid or how they are selected, despite the 'up to six' cap implying kinds drives that count.

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 resource (creates still-image variants from one main-video frame at a program timestamp) plus a clear limit of six and the key side effect of saving as project assets rather than placing in the edit. It does not differentiate itself from siblings like render_variants, animate_still, or pick_still, which share the visual-variant space, so it falls short of a 5.

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 (one frame at a timestamp, up to six variants, results not added to the timeline), which lets an agent infer this is a variant-generation step rather than an editing step. There is no explicit when-to-use or when-not-to-use guidance, and no naming of the alternatives (render_variants, pick_still, animate_still) that an agent would need to choose correctly.

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