Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Render a design and look at it now

capture_design_screenshot
Idempotent

Render one design variation NOW and attach its screenshot, so you can check a design you just imported or edited before showing it to anyone. Takes about 30-40 seconds; a design that already has a render answers at once (send force: true after an edit to render it again). Use this instead of waiting when list_variations says thumbnails are pending or get_render_diagnostics has no screenshot. Omit index for the active design.

Input Schema

NameRequiredDescriptionDefault
forceNoRender again even if a screenshot exists (e.g. after an edit)
indexNoVariation index from list_variations. Defaults to the active design.
site_idYesThe site whose design to render
viewportNoDefault desktop
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.7/5.0
Behavior5/5

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

Adds context beyond annotations: ~30-40 second cost, the caching behavior that a previously rendered design returns at once, and the `force: true` escape hatch after an edit. That latency and caching model is precisely what an agent needs to decide whether to call it now or wait.

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 sentences, front-loaded with the action, then cost, then routing guidance. No filler and no repeated title/schema content.

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 5-param mutation-like render tool with no output schema, the description covers what is produced (an attached screenshot), how long it takes, when the result is instant, and how to force a refresh. No important gap remains for correct invocation.

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 coverage is 100%, so the schema already documents force, index, viewport and site_id. The description only reiterates the force-after-edit and default-index behaviors, adding marginal meaning rather than new syntax or constraints.

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 ("Render one design variation ... and attach its screenshot") plus a scope qualifier ("one", "NOW"). It is unmistakable against siblings like generate_design_variation (creates variations) and get_render_diagnostics (read-only diagnostics).

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 when-to-use triggers: after importing or editing a design, before showing it to anyone, or when list_variations says thumbnails are pending and get_render_diagnostics has no screenshot. It also names the alternative behavior it replaces ("use this instead of waiting").

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