Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Change a film's playback speed

set_studio_video_speed
Idempotent

Speed a finished film up or slow it down: speed from 0.25 to 4 (1 is normal; "a bit faster" is about 1.25). The picture, the voice and the captions move together and the voice keeps its natural pitch. Optional remove_pauses: true also cuts the silent pauses (false puts them back). FREE: nothing is generated or charged — the film is put together again from what is already made. For several films, call once per film. Answers ready: true with export_url, or ready: false while it is being put together (poll get_studio_video until ready; never say it is done before). Other changes to a film go to studio_video_message.

Input Schema

NameRequiredDescriptionDefault
speedYesPlayback speed: 0.25–4, 1 = normal
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
project_idYesThe film's project id (list_creations kind "video", or create_motion_project). The bare project id or the library id ("studio-video:<uuid>" from list_creations / find_creation) both work.
remove_pausesNotrue: also cut the silent pauses; false: put cut pauses back. Omit to leave them as they are.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond annotations: it discloses that the operation is free ("nothing is generated or charged — the film is put together again"), that picture/voice/captions stay in sync and pitch is preserved, and that remove_pauses=false restores cut pauses. It also describes the async contract (ready true/false) and warns never to claim completion before polling, which annotations do not cover.

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?

Front-loaded with the action and the value range, then layered: side effects, cost, batching, return contract, sibling routing. Dense but no sentence is redundant, and each one carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by explaining the ready/export_url return shape and the polling loop. Combined with the cost and multi-film guidance, an agent has everything needed to call and follow up correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretation the schema lacks: 0.25–4 with 1 as normal and "a bit faster" ≈ 1.25, plus remove_pauses false meaning "put back" rather than simply unset. project_id and user_goal get no description-level treatment, keeping it just short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Speed a finished film up or slow it down") with the operating range baked in. It explicitly routes everything else to studio_video_message, so an agent can tell it apart from the sibling without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (speed changes on a finished film), when-not-to ("Other changes to a film go to studio_video_message"), and per-film batching guidance ("For several films, call once per film"). It also names get_studio_video as the polling alternative for the async result.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mondovo 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