Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Approve a video plan

approve_studio_video_plan

Approve the plan the director put up — the only step that makes anything. Send pending_plan.proposal_id and its quoted_credits as expected_credit_cost; a mismatch is refused. Plans quoted at 0 (captions, end cards, trims, library music) are free; drawn beats, a custom music track, text behind the speaker and re-voicing are priced on the plan. A paid plan spends Creative Credits against this connection's daily cap: NEVER approve one without the user's explicit go-ahead on that price. Optional resolution picks one of pending_plan.alternatives — then send that alternative's credits. A plan with pack: true is separate shots: optional shots (its shots[].shot_id values) approves only those, and expected_credit_cost is then the sum of their credits; unchosen shots are not made or charged. If the plan cannot be applied (request_failed), its message says why, anything it charged is refunded, and the plan stays waiting to be approved again. Afterwards poll get_studio_video until ready.

Input Schema

NameRequiredDescriptionDefault
shotsNoPack plans only: pending_plan.shots[].shot_id values to make. Omit for every shot
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.
resolutionNoOne of pending_plan.alternatives[].resolution, to take that size instead
proposal_idYespending_plan.proposal_id from get_studio_video or studio_video_message
expected_credit_costYespending_plan.quoted_credits (0 for a free plan)

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.9/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that approval spends Creative Credits against a daily cap, that a mismatched expected_credit_cost is refused, that free versus priced items differ, and that on request_failed the charge is refunded and the plan remains pending. That refund-and-retry detail is essential given idempotentHint=false, since it tells the agent a retry is safe.

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?

The purpose and the credit-safety warning are front-loaded, and every sentence carries operational information rather than filler. It is dense and a few clauses run long (the pack/shots sentence stacks three rules), but nothing is redundant.

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 6-parameter, non-idempotent, credit-spending mutation with no output schema, the description covers the inputs, the failure contract, the refund guarantee, and the required next poll. An agent could call this correctly and recover from errors using the description alone.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds cross-parameter rules the schema cannot express: expected_credit_cost must equal pending_plan.quoted_credits or the call is refused, resolution must come from alternatives and changes which credit figure to send, and shots requires summing the chosen shots' credits and omitting unchosen ones.

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 ("Approve the plan") and immediately stakes out exclusive scope with "the only step that makes anything," which distinguishes it from the drafting siblings like plan_video, edit_studio_video_storyboard and get_studio_video. An agent knows exactly what this call does and what it does not.

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?

Gives explicit preconditions ("NEVER approve one without the user's explicit go-ahead on that price"), names the alternative path ("resolution picks one of pending_plan.alternatives — then send that alternative's credits"), covers the partial-approval case via shots, and prescribes the follow-up ("Afterwards poll get_studio_video until ready"). Nothing is left to inference.

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