Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Choose how collection items open

set_collection_item_display
Idempotent

Choose how a visitor opens ONE item of a collection when they click it in a list or grid: "page" (its own full page — the default) or "modal" (a quick-view pop-up over the list, with photo, description, price, add to cart and a link to the full page). Works for any collection. Each item keeps its own page either way, so links and search are unaffected. The response carries tradeoffs — relay them to the owner. The preview shows the change at once; the live site updates on the next publish_site. list_collections reports each collection's current item_display.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site the collection belongs to
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.
item_displayYes"page" = own page, "modal" = quick-view pop-up.
collection_typeYesThe collection's slug, as list_collections returns it (e.g. "blog", "menu", "products", "faqs").

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

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

Beyond the idempotent/non-destructive annotations, it discloses that the preview updates immediately while the live site only changes on the next publish_site, that links and search are unaffected, and that the response carries `tradeoffs` to relay to the owner. These are exactly the operational facts an agent needs before invoking a mutation.

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?

Purpose and option definitions are front-loaded, followed by consequence, response, and timing notes. Every sentence carries actionable information with no 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?

With no output schema, the description compensates by explaining the `tradeoffs` field and the preview/publish timing. Combined with the 100% schema coverage, an agent has everything needed to call and interpret the result.

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 the schema already documents site_id, collection_type, item_display, and user_goal. The description reinforces the item_display semantics and the collection_type lookup pattern but adds little the schema does not already say, so 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?

The description gives a specific verb (choose/set) and a precisely scoped resource (how one item of a collection opens), and it spells out the two enum values with concrete consequences. An agent can distinguish this from update_collection_item (which edits item content) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the context clearly (works for any collection, affects list/grid click behavior) and points to list_collections to read the current setting before changing it. It stops short of explicit when-not-to-use guidance or naming a sibling alternative, so it is strong but not complete.

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