Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Open a short for direct editing

open_short
Read-onlyIdempotent

Opens a generated short by child project ID or by its one-based card number and explicit parent project ID. Returns the child identity and state for direct editing; it does not start or delegate to another editing agent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_short"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNoOne-based card number within the explicit parent project's shorts board.
child_project_idNoGenerated child project ID.
parent_project_idNoShorts board project; required when selecting by card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / card / description
      Previous value: -"1-based card number from shorts_status."New value: +"One-based card number within the explicit parent project's shorts board."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive, closed world), so the bar is lower. The description still adds genuine context the flags do not: what 'open' actually means here (returns child identity and state for editing) and the negative guarantee that it does not spawn or hand off to another editing agent.

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: the addressing mechanism comes first, then the return/behavioral clause. No filler, no repetition of the title, and the negative constraint is placed where it reads as a scope boundary.

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?

There is no output schema, and the description at least characterizes the return ('child identity and state'), which is enough for a simple read tool whose annotations already carry the safety profile. A little more on what 'state' contains, or on error behavior when card and parent mismatch, would make it complete.

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 100%, so all three parameters are already documented, and the description largely restates them. It does add mild emphasis on the mutual-exclusivity/conditional-dependency ('explicit parent project ID' required when selecting by card), but offers no format or edge-case detail beyond the schema.

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 ('Opens a generated short') and spells out the two addressing modes (child project ID, or one-based card number plus explicit parent project ID), so an agent knows exactly what the call targets. It does not name the sibling it differs from (e.g., open_project, shorts_status), which keeps it 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?

The description clarifies scope behaviorally ('for direct editing; it does not start or delegate to another editing agent'), which tells the agent this is not a workflow-launching call. However, it never says when to prefer this over open_project or shorts_status, nor any prerequisite ordering, so routing is largely implied.

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