Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Suggest site icons (favicons)

generate_favicon_options
Idempotent

Design up to four icon ideas for the site's browser tab, bookmarks and search results, from its brand name, colours and heading font, plus the plain letter icon ("monogram"). One AI image; options are cached per site, so calling again returns the same set unless regenerate is true. Ideas whose lettering does not match the brand are dropped. Returns preview URLs — show them, then call set_favicon with the chosen id.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site to act on
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.
regenerateNoDraw a fresh set even when options are already cached. Costs another image.

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

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

Goes well beyond the annotations by disclosing cost ('One AI image', regenerate 'Costs another image'), cache scoping per site, quality filtering ('Ideas whose lettering does not match the brand are dropped'), and the return shape (preview URLs). Annotations only cover readOnly/idempotent/openWorld, so this added context is genuinely valuable.

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 tight sentences, front-loaded with what it produces, then caching behaviour, then the required next step. No filler and no repetition of the title.

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?

Despite having no output schema, the description states what is returned (preview URLs) and what to do with them. Caching, cost and the hand-off to set_favicon cover everything an agent needs to call this correctly.

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 baseline is 3; the description adds real semantics for `regenerate` (fresh draw vs cached set, extra image cost) that go slightly past the schema's cost note. `user_goal` is not mentioned at all, leaving a small gap.

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?

Specific verb and resource: 'Design up to four icon ideas for the site's browser tab, bookmarks and search results' from brand name, colours and heading font. It names the concrete input sources and the fallback monogram, so it is clearly distinguished from neighbours like create_logo, plan_logo, explore_image_concepts and set_favicon.

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?

Explicit sequencing: 'Returns preview URLs — show them, then call set_favicon with the chosen id,' which routes the agent to the correct follow-up sibling. It also states the caching/repeat-call condition ('returns the same set unless `regenerate` is true'), removing ambiguity about re-invocation.

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