Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Change a site's theme

apply_theme
Idempotent

Change the look across EVERY page of one design at once: colours, fonts, corner radius, or a complete ready-made preset. Send only what should change. For a change to one section or page use refine_site instead. Publish for visitors to see it.

Input Schema

NameRequiredDescriptionDefault
colorsNoColours to change, as hex values (e.g. {"primary": "#1d4ed8"}). Only the ones given change.
presetNoA complete ready-made theme. One of: neobrutalist, neobrutalist-dark, minimal, minimal-dark, corporate, corporate-dark, playful, luxury, cyberpunk, cyberpunk-dark, editorial, editorial-dark, retro, retro-dark. Replaces colours, fonts, borders and shadows together.
bordersNoCorner radius and border width as CSS lengths (e.g. {"radius": "12px"}).
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.
typographyNoFonts to change, by Google Font name (e.g. {"headingFont": "Playfair Display"}).
variation_idNoThe design to change. Omit for the site's live design.

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.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent write, so safety is covered. The description adds genuinely non-structural behavior: changes are partial by default and are not visible to visitors until the site is published. It does not discuss auth, rate limits, or whether a preset wipes prior custom values, which keeps it short of a 5.

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?

Four tight sentences, front-loaded with the scope-defining clause in capitals, then the partial-update rule, the sibling exclusion, and the publish consequence. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-param nested write tool with no output schema, the description covers scope, partial-update semantics, the routing alternative, and the publish dependency. It omits what the tool returns and whether a preset overrides explicit colors/fonts sent in the same call, a real ambiguity but a minor one.

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 description coverage is 100%, so both the field-level docs and the enum values are already spelled out, including that colors is partial and preset replaces everything. The description's 'send only what should change' and 'complete ready-made preset' largely restate that, adding little new syntax or format guidance. Baseline 3 is appropriate.

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 ('Change the look') with explicit scope ('across EVERY page of one design at once') and enumerates the dimensions affected: colours, fonts, corner radius, or a preset. It names the sibling it must not be confused with (refine_site), so an agent can pick correctly without inspecting schemas.

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?

Explicitly routes the agent: use this for site-wide design changes, use refine_site for a single section or page. Adds a partial-update instruction ('Send only what should change') and a required follow-up ('Publish for visitors to see it'), leaving no ambiguity about when and how to use it.

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