Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Render variants

render_variants

Renders three typography treatments of an existing lockup as still images on the actual frame. Returns comparison images without changing 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": {
      "project_id": "<project_id>"
    },
    "name": "render_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
idNo
axisNo
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

B3.2/5.0
Behavior3/5

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

The annotations already declare non-destructive, non-read-only, non-idempotent, closed-world behavior. The description adds meaningful context that it returns comparison images and does not alter the edit, which helps an agent understand the side-effect boundary. But it also says 'three' variants while the n parameter accepts 2–4, creating a behavioral ambiguity the annotations cannot resolve.

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 short sentences, front-loaded with the action and scope, followed by the key no-edit-change guarantee. Every sentence earns its place and there is no filler.

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?

For a four-parameter tool with only 25% schema description coverage and no output schema, the definition leaves important gaps: the meaning of n vs. 'three,' what axis='voice' controls, and what id refers to. The no-edit-change note is useful, but overall the description is too thin to let an agent invoke this correctly without guessing at 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?

Schema description coverage is only 25%, so the description carries most of the burden for explaining four parameters. It hints that id is an existing lockup and project_id is the target frame, but it never explains n, axis, or why n can range from 2 to 4 when the description fixes three treatments. The low-coverage schema is not compensated for.

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 clear verb and resource: it renders typography treatments of an existing lockup as still images on the actual frame. That is more specific than the name alone and distinguishes it from additive typography siblings like add_typeset or set_typeset. It stops short of naming a close alternative such as make_variant_set or render_preview, so it is not 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 'returns comparison images without changing the edit,' which suggests a safe preview-style comparison flow. However, it never says when to choose this over render_preview, make_variant_set, or any other typography sibling, and it gives no prerequisites or exclusions. That is adequate implied guidance but not explicit routing.

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