Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Change a built-in UI label

set_runtime_text
Idempotent

Set the wording of ONE built-in shop label on this site for one language (e.g. make the cart button read "Buy now", or fix a poor translation of "Add to Cart"). Needs the exact key from list_runtime_text — never invent one; an unknown key is refused with the closest valid keys. clear: true removes the custom wording and goes back to the automatic translation. Reaches the live site on the next publish. For the site's own copy use patch_variation_content.

Input Schema

NameRequiredDescriptionDefault
keyYesThe label's exact key from list_runtime_text, e.g. "cart.addToCart"
clearNoRemove the custom wording for this key
valueNoThe wording to show. Required unless clear is true
site_idYesThe site, from list_sites
languageNoLanguage the wording is for. Defaults to the site's own language
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 only declare the safety profile (not read-only, idempotent, non-destructive); the description adds genuinely non-obvious behavior: unknown keys are refused with the closest valid keys, clear:true restores the automatic translation, and changes do not go live until the next publish. That is exactly the extra context annotations cannot carry.

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 sentences, each carrying a distinct load-bearing fact: scope, key prerequisite, revert semantics, activation timing, plus the sibling redirect. The most critical constraint (use ONE label, exact key) is front-loaded.

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 6-parameter mutation tool with no output schema, the description covers prerequisites, failure mode, revert, and when effects appear. The only gap is that it says nothing about the response or whether language defaults are validated, which is minor given the schema documents language defaults.

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 every parameter is already documented, including key provenance and clear's revert meaning. The description reinforces the key constraint and the clear behavior but adds no syntax, format, or length guidance beyond the schema, so the baseline 3 applies.

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 — set the wording of ONE built-in shop label for one language — and immediately scopes it away from the site's own copy by naming patch_variation_content. An agent can distinguish it from list_runtime_text (the reader) and patch_variation_content (page copy) without opening any 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?

Explicit routing rules: obtain the key from list_runtime_text, never invent one, and use patch_variation_content for the site's own copy. It also documents the revert path (clear: true) and the activation condition (live on next publish), leaving nothing 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 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