Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Stop making the film

stop_studio_video
DestructiveIdempotent

Stop a film while it is being made (get_studio_video button.making.stoppable). Scenes that have not started are called off and their credits refunded; scenes already being made finish, and the film is put together from what is made. Does not spend.

Input Schema

NameRequiredDescriptionDefault
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_idYesProject id from create_motion_project. The bare project id or the library id ("studio-video:<uuid>" from list_creations / find_creation) both work.

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. Changed3 schema fields changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id from create_motion_project"New value: +"Project id from create_motion_project. The bare project id or the library id (\"studio-video:<uuid>\" from list_creations / find_creation) both work."
    • removedInput schema / properties / project_id / format
      Removed value: -"uuid"
    • addedInput schema / properties / project_id / pattern
      Added value: +"^(?:studio-video:)?[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by explaining precisely what is destroyed (unstarted scenes are called off and refunded) versus what survives (started scenes finish and the film is assembled from made material), plus the explicit "does not spend" credit statement. This resolves the ambiguity a bare destructive flag would leave.

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 action and its precondition, then the consequences, then the credit effect. No filler and nothing repeated from the schema or annotations.

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?

For a two-parameter, no-output-schema mutation, the description covers precondition, partial-destruction semantics, refund behavior, and cost. The only minor gap is what the caller gets back after stopping (e.g., whether a partial film artifact is produced), though "the film is put together from what is made" implies it.

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 description coverage is 100% and both parameters are fully documented in the schema, including the project_id format variants and the optional user_goal. The description adds no parameter-level meaning, so baseline 3 applies.

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 (stop a film) and constrains it to an in-progress state ("while it is being made"), which distinguishes it from get_studio_video and from creation/edit siblings. The parenthetical pointer to the `button.making.stoppable` flag makes the exact precondition checkable.

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

Usage Guidelines4/5

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

The parenthetical tells the agent to verify the film is in a stoppable state via get_studio_video before calling, which is an actionable precondition. It stops short of naming alternative actions (e.g., letting it finish, or editing the plan) that an agent might weigh against stopping.

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