Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Set the video editing budget

set_studio_video_edit_budget
Idempotent

Authorize or pause this film's persistent automatic editing allowance, only for a cap the user explicitly chose. This changes permission only: it charges nothing, starts no edit, and never requires a fresh Make approval for requested paid edits that fit within the active cap. Set cap_credits to a whole number up to the limit, or null to pause. Use the current editing_budget.revision as expected_revision; a changed revision is refused. The cap is a ceiling, unused credits are never charged, and each edit reports its actual charge or pending payment.

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.
cap_creditsYesPersistent cap for automatic requested edits, or null to pause
expected_revisionYesediting_budget.revision from get_studio_video

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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing that this changes permission only, charges nothing, starts no edit, and removes the need for a fresh Make approval for edits within the cap. It also discloses the optimistic-concurrency refusal behavior and that unused credits are never charged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and the key constraint, then moves to parameter mechanics and billing semantics. Every sentence carries information, though the closing sentence on ceiling/unused credits/charge reporting is denser than strictly necessary.

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?

For a mutation tool with no output schema, the description covers what is needed to call it correctly: the permission-vs-charge distinction, the pause path, the concurrency precondition, and what downstream edits report. An agent has no significant open question before invoking it.

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 real meaning: `expected_revision` triggers a refusal if the revision changed, and `cap_credits` is a ceiling rather than a spend. It repeats the schema's 'null to pause' wording rather than extending it, which holds it at 4.

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 pair and resource: 'Authorize or pause this film's persistent automatic editing allowance.' It is unmistakably distinct from siblings like get_studio_video, set_studio_video_speed, or edit_studio_video_script, and the scope ('only for a cap the user explicitly chose') is front-loaded.

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?

Gives clear conditions: set `cap_credits` to a whole number to authorize, null to pause, and 'Use the current `editing_budget.revision` as `expected_revision`; a changed revision is refused.' The exclusion 'only for a cap the user explicitly chose' also constrains usage. No sibling is named as an alternative, which keeps it from a 5.

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