Mondovo

Make private image concepts

explore_image_concepts

Idempotent

Generate 1–3 private image concepts for a hero, a section or an image replacement, so the user can compare directions before anything on the site changes. SPENDS Creative Credits: call plan_image_concepts first and send its credits as expected_credit_cost with a stable idempotency_key; a different price is refused with nothing charged. Failed concepts are refunded. The site is NOT changed — to use a concept, call apply_image_replacements with its concept_library_id (free).

Input Schema

Name	Required	Description
`count`	No	How many concepts (1–3, default 3). Must match the plan_image_concepts quote.
`purpose`	Yes	What the concepts are for.
`site_id`	Yes	The site to act on
`image_id`	No	The image a concept might replace (from plan_image_regeneration).
`page_slug`	No
`user_goal`	No	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.
`exact_text`	No	ONLY for words physically part of the artwork (a sign, a label). Omit otherwise.
`aspect_ratio`	No	Default 16:9 for a hero, 4:3 otherwise.
`content_path`	No
`original_url`	No	The current image's URL, for a later apply.
`section_name`	No
`variation_id`	No	The design to work on. Omit for the site's live design.
`direction_brief`	Yes	A concrete visual direction: subject, composition, mood, palette, brand fit. Never page copy or UI — headings and buttons stay real text on the page.
`idempotency_key`	Yes	Stable key for this attempt; reuse it on a retry so nothing is charged twice
`expected_credit_cost`	Yes	`credits` from plan_image_concepts for this count

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

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"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say non-readonly, idempotent, non-destructive, open-world; the description adds the behavior that actually matters: it spends Creative Credits, refuses a price mismatch with nothing charged, refunds failed concepts, and requires a stable idempotency key to avoid double charging. That is substantive cost/failure/safety context beyond the annotations.

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-loaded with purpose, then the credit prerequisite, then the failure/refund policy and the no-change next step — every clause is actionable. It is dense and semicolon-chained, which costs it a point on readability, but no sentence is filler.

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 15-parameter, credit-spending, no-output-schema tool, the description covers the full decision loop: when to call it, the required quote, the failure/refund semantics, and how to act on the result via concept_library_id. An agent could invoke this correctly without further guidance.

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 80% so baseline is 3, but the description adds real meaning for the two load-bearing parameters: expected_credit_cost must come from the plan_image_concepts quote, and idempotency_key must be reused on retry so nothing is charged twice. It does not clarify the purpose enum values or how image_id vs original_url interact, which keeps it below 5.

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 (generate), resource (private image concepts), and scope (1–3, for a hero/section/image replacement, for comparison before anything changes). An agent can distinguish this from plan_image_concepts (quoting) and apply_image_replacements (applying) without opening either schema.

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 prerequisites ('call plan_image_concepts first and send its credits as expected_credit_cost'), an explicit exclusion (site is NOT changed), and an explicit alternative for the follow-on action (apply_image_replacements with concept_library_id, free). 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 tools Inspect

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

Need Help?