Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Create a collection

create_collection
Idempotent

Create a new catalog collection on a site that has a design — products, courses, events, jobs, properties, rooms, portfolio pieces. Mondovo sets up its fields, generates a detail-page template in every design plus a listing page, and seeds starter items. Takes up to a few minutes and costs no credits. If the collection already exists nothing is created (already_existed) — add items to it instead. Publish the site for its pages to go live. ON A SITE THAT STILL HOLDS SEVERAL DESIGNS this builds the site: Mondovo copies the chosen design into the working site (or reuses the copy made earlier), adds to that, and the response carries its new site_id and a build_transition — relay its tell_user and use the new site_id from then on. Pass variation_id for the design the user picked; omitted, Mondovo uses the design already built or the only one edited, and otherwise answers choose_design so you can ask the user.

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.
sample_itemsNoItems the user gave you to start with (1-5 is typical). Omit to seed from the site's existing content or generic starters.
variation_idNoOn a site that still holds several designs: the design to build the site from (from list_variations). Mondovo copies it into the working site and adds to that. Omit on a site that is already built.
collection_typeYesLowercase snake_case slug for the new collection: products, menu, rooms, courses, properties, events, jobs, faqs, downloads, portfolio, team — or a descriptive custom one like vintage_watches.

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. Changed1 schema field changed
    • addedInput schema / properties / variation_id
      Added value: +{
+  "description": "On a site that still holds several designs: the design to build the site from (from list_variations). Mondovo copies it into the working site and adds to that. Omit on a site that is already built.",
+  "maxLength": 200,
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, idempotent=true): it discloses duration ("up to a few minutes"), cost ("costs no credits"), side effects (fields, detail-page template in every design, listing page, seeded items), the idempotent `already_existed` outcome, and that a multi-design build returns a new `site_id` plus a `build_transition` whose `tell_user` must be relayed.

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-loads the core action and its cost/duration, then escalates to the edge cases; nearly every sentence carries unique operational information. The uppercase multi-design paragraph is dense and slightly run-on, but it is load-bearing rather than padding.

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 still documents the meaningful return signals (`already_existed`, new `site_id`, `build_transition.tell_user`, `choose_design`), which is exactly what an agent needs to handle the response 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 earns above that by explaining variation_id omission behavior (use built/only-edited design, else answer `choose_design`) and the semantic shift of `site_id` after a multi-design build — neither of which the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a new catalog collection") and enumerates concrete collection types, so the agent knows exactly what gets created. It does not, however, distinguish itself from the sibling `create_dynamic_collection` / `list_dynamic_collections`, which an agent could reasonably confuse with this.

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?

Gives real when/when-not guidance: it names the alternative path when the collection exists ("add items to it instead"), notes that publishing is a separate step, and explains the multi-design branch with a fallback to `choose_design`. The only missing routing is versus the dynamic-collection siblings.

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