Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Price an animated carousel

plan_carousel_animation
Read-onlyIdempotent

FREE quote for turning a FINISHED carousel (its job_id from create_visual — one made today or any older one) into an animated carousel. The owner has already seen the still slides; for each slide they choose a motion: "still" (stays a picture, free), "animate" (the slide moves by itself — steam, light, drifting objects — from its own picture; note says what moves), or "pass_through" (a character crosses the slide from left to right, so swiping carries them across the deck; the first slide starts with them standing, the last ends with them arriving). Slides you leave out stay still. Each moving slide is a short video clip and costs 12 credits; still slides cost nothing. The first animation of a carousel also adds a once-only deck charge: an animated carousel is 15 credits for the deck, and what the carousel already cost counts toward it (deck_credits). Returns the plan and credits — show the owner the price and get their OK, then call animate_carousel with expected_credit_cost = credits. Only Instagram takes video slides in a carousel.

Input Schema

NameRequiredDescriptionDefault
job_idYesThe finished carousel job id
slidesYesPer-slide motion; unmentioned slides stay still
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.

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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description is fully consistent with that by calling this a FREE quote. It adds substantial behavioral context beyond annotations: per-moving-slide cost, the once-only deck charge, the fact that prior carousel cost counts toward it, and that only Instagram supports video slides in carousels.

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 description is front-loaded with the quote purpose and keeps the cost model and next step together. It is somewhat dense and could be more scannable, but nearly every sentence carries necessary pricing or routing 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?

For a planning/pricing tool with no output schema, the description explains what is returned (`plan` and `credits`), how the price is derived, and what to do next. Combined with complete schema descriptions, it gives the agent enough to call this correctly and interpret the result.

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. The description still adds meaningful semantics for `slides.motion`, explaining `still`, `animate`, and `pass_through`, clarifying that unmentioned slides stay still, and describing what `note` should contain; only `user_goal` is left entirely to the schema.

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?

The description states a specific action — producing a FREE quote that turns a finished carousel into an animated carousel — and names the input source (`create_visual` job_id) and the sibling follow-up (`animate_carousel`). An agent can distinguish this pricing/planning step from the actual animation call without opening the schema.

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?

It gives clear usage context: the owner has already seen still slides, per-slide motion choices are made now, the returned `credits` should be shown to the owner for approval, and then `animate_carousel` should be called with `expected_credit_cost`. It does not explicitly exclude alternatives such as `preview_carousel_animation`, but the sequencing is otherwise clear.

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