Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Make service-area pages

bulk_generate_service_location_pages
Idempotent

Have our AI write one local SEO page per service × location pair (e.g. "boiler repair" × "Leeds") and save them as DRAFT pages. At most 10 per call; for more, call again with the next pairs (pages that already exist are skipped, so a repeat never duplicates). A page whose slug already exists is skipped, as is one whose copy does not actually talk about its location; the response lists what was created and what was skipped and why. Nothing goes live and no build starts. One AI call per page, so a full batch takes a few minutes; counts toward the hourly AI limit. 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
combosYesservice and location for each page; target_keyword defaults to "service location"; cell_key optionally aligns it with a strategy cell
site_idYesThe site, from list_sites
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 already cover safety, and the description adds important context: nothing goes live and no build starts, one AI call per page, batches take minutes, and the call counts toward the hourly AI limit. It also discloses skip reasons and the multi-design complication where a new site_id and build_transition appear and must be relayed, which is behavior an agent could not infer.

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?

Purpose and the 10-per-call limit come first, then skip behavior, then side effects, and then the multi-design case. It is dense and long, but nearly every sentence carries operational information. The all-caps multi-design paragraph is heavy, yet it is justified by the complexity.

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?

The definition covers side effects, rate limits, latency, skip and duplicate handling, response contents, and the site-rebuild transition with its site_id change. Together with a 100%-documented schema, an agent has everything needed to call it and handle the response.

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 would be 3. The description still adds meaning beyond the schema, including how combos map to pages and the fallback rules for variation_id ('uses the design already built or the only one edited, otherwise answers choose_design'), though it does not clarify target_keyword or cell_key beyond the schema.

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: 'have our AI write one local SEO page per service × location pair ... and save them as DRAFT pages', with a concrete example. This clearly separates it from siblings like add_page, add_pages, and generate_alternative_pages.

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 batch rule ('at most 10 per call; for more, call again with the next pairs'), explicit dedupe behavior ('pages that already exist are skipped, so a repeat never duplicates'), and explicit guidance for variation_id, including the fallback that returns choose_design so the agent can ask the user.

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