Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

List a site's forms

list_forms
Read-onlyIdempotent

Every form on one design of a site — forms on pages, form components and multi-step quiz forms — with their fields (a field's options are the choices visitors see, including any price written in them) and submission settings. Read this first when the person asks what a form shows or says a field, price or amount is missing from it; it answers from the form itself. Settings: webhook URL, success message, redirect, CRM contact creation, notification emails and the auto-acknowledgement email, plus how many submissions each has received. email_notifications.effective_recipients explains who is actually notified; an unconfigured form defaults to the site owner even when its stored recipients list is empty. popup_forms lists the popup forms buttons can open; pass one's id as link_cta's form_id, and its slug to get_form / update_form_settings like any other form slug.

Input Schema

NameRequiredDescriptionDefault
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_idNovariation_id of the design to read or change (from list_variations). Omit for the site's chosen design.

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

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

Annotations already cover read-only, idempotent, and non-destructive safety, while the description adds return semantics: email_notifications.effective_recipients explains actual notification behavior, an empty stored recipient list defaults to the site owner, and popup_forms are callable via link_cta. It does not discuss pagination or ordering, but supplies notably more context than the annotations alone.

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?

The description is front-loaded with the resource and scope, then adds usage guidance, settings details, and popup-form linkage. It is dense and uses long semicolon-linked sentences, but most details earn their place by clarifying returned semantics.

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?

With no output schema, the description sufficiently explains the shape and meaning of returned forms, settings, effective recipients, and popup forms. It omits possible pagination or ordering details, but otherwise gives an agent enough information to call and interpret the tool.

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?

All three parameters are fully documented in the schema, including site_id, variation_id, and user_goal. The description does not add syntax or selection guidance beyond noting that results are scoped to one design, so the baseline 3 is appropriate because the schema carries parameter meaning.

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 that the tool lists every form on one design of a site, enumerates included form types (page forms, form components, multi-step quiz forms), and names the returned content such as fields, options, and submission settings. The scope is specific enough to distinguish it from get_form, which is referenced as a downstream tool.

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 a clear first-use trigger: read this first when someone asks what a form shows or reports a missing field, price, or amount. It also explains how popup_forms IDs and slugs feed link_cta, get_form, and update_form_settings, but stops short of an explicit when-not rule or direct guidance on when to prefer get_form for a single known form.

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