Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Add several pages to a site

add_pages

Add multiple inner pages to an existing site in one call (up to 10). Each page is generated to match the site's existing theme. Use this to stand up a full set of pages (About, Services, Contact, etc.) at once. The site must already have a design. 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 (from list_variations) 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. Returns a job_id immediately; poll get_job every ~10s until its status is "completed". Pages are generated with bounded parallelism, so a batch of 10 takes minutes, not 10x one page. Per-page failures are reported individually in the job's failed array — one bad page does not abort the rest, so a "completed" job can still carry failures worth reporting to the user. These pages are NOT added to the site's menu — to link them, patch_variation_content navigation with the full edited array (or use add_page per page with nav_placement).

Input Schema

NameRequiredDescriptionDefault
pagesYesThe pages to create (1-10)
site_idYesThe site to add the pages 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.
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.

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

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

Annotations only give generic flags; the description supplies the real behavior an agent needs: returns a `job_id` immediately, poll `get_job` every ~10s, bounded parallelism makes 10 pages take minutes, and a 'completed' job can still carry per-page failures in a `failed` array. It also discloses the non-obvious side effect that building can migrate the working site to a new `site_id` with a `build_transition` message to relay.

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?

It is front-loaded with purpose and batching before the edge cases, and nearly every sentence carries operational information. It is dense and slightly rambling in the design-transition paragraph, but that reflects genuine conditional complexity 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?

There is no output schema, so the description carries return-value burden and does so: `job_id`, polling target and cadence, `failed` array, `site_id`/`build_transition` on unbuilt sites, and `choose_design` on ambiguous design. The menu-linking caveat closes the main remaining ambiguity.

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 the baseline is 3, but the description adds real meaning beyond the schema for `variation_id`: what happens when it is omitted, that Mondovo reuses the already-built or only-edited design, and that it otherwise returns `choose_design` so the agent must ask the user. It also clarifies the batch limit and per-page structure contextually.

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 opening sentence states a specific verb and resource with scope ('Add multiple inner pages to an existing site in one call (up to 10)') and immediately distinguishes the batch case from the single-page sibling. An agent can tell what it does without reading the 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?

It names explicit alternatives and the conditions that select them: use add_page per page when you need `nav_placement`, use patch_variation_content `navigation` to link pages, and pass `variation_id` only on a site that still holds several designs. The prerequisite ('The site must already have a design') is stated up front.

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