Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Compose panels

compose_panels

Renders two or three independent video columns side by side on a black 16:9 canvas. Each column may contain a sequence of clips. The result is a project video asset, not an automatically inserted program segment.

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": {
      "columns": "<columns>",
      "project_id": "<project_id>"
    },
    "name": "compose_panels"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsYes
duration_sNo
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.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the output is a project video asset rather than an inserted program segment, which tells the agent a follow-up placement step is needed. It does not disclose what happens on column count mismatch, how duration_s interacts with clip lengths, or whether re-invocation duplicates assets.

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, front-loaded with the rendering behavior, then the column structure, then the output-type caveat. No filler and no repetition 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 mutation tool with no output schema and an untyped array parameter, the description covers the core concept but leaves the clip reference format, duration semantics, and column-count validation unstated. An agent could invoke it, but would likely need to guess at the structure of each column entry.

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 33%: only project_id is documented, and its description already explains the navigation-pointer caveat. The description partially compensates by explaining that columns are independent video columns (two or three) each containing a sequence of clips, which gives shape to the otherwise untyped array. duration_s remains entirely unexplained in both schema and description.

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 gives a specific verb and resource ('Renders two or three independent video columns side by side on a black 16:9 canvas') and constrains the count to two or three, which is more than the name alone conveys. It also distinguishes the output from an auto-inserted program segment, separating it from insertion-style siblings, though it never names a concrete alternative such as add_collage or set_composite.

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: the agent can infer this is the tool for side-by-side multi-column layouts, and the closing sentence hints the result must be placed separately. There is no explicit when-to-use versus when-not-to-use guidance and no named alternative among the many composition siblings (add_collage, set_composite, add_overlay).

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