Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Automation overview

get_automation_overview
Read-onlyIdempotent

Read live Phone & SMS settings: the configured Twilio phone number, connection state, business and campaign registration statuses. Use this when asked what the phone number is or whether SMS is set up; site/SEO settings do not contain it. Also lists every built-in automation (review requests, booking reminders, lead auto-reply, order and shipping notices, abandoned-cart nudges), whether it is ON, its triggers, send counts and editable templates, plus custom journey counts. Some automations are ON by default without stored rows.

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.

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.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is free. The description does add a genuinely useful behavioral caveat — 'Some automations are ON by default without stored rows' — warning that stored config may not equal effective state. However it says nothing about auth requirements, size of the response, or whether registration statuses are live-queried or cached.

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 phone/registration content lead, with the automation inventory following. The long parenthetical list of automation types is somewhat dense but each item conveys real scope; only minor trimming is warranted.

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 correctly carries the return-value burden by enumerating what comes back: phone number, connection state, registration statuses, per-automation state/triggers/counts/templates, and custom journey counts. That is sufficient for an agent to decide to call it 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 coverage is 100% and both parameters are self-documented, so the baseline of 3 applies. The description implies site scoping but adds no syntax, format, or guidance on the optional user_goal field.

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?

Names a specific verb and a concrete resource set: live Phone & SMS settings (number, connection state, registration statuses) plus the full automation inventory. It also enumerates the automation categories and per-automation fields (ON state, triggers, send counts, templates), so an agent can tell this apart from generic settings readers.

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?

Explicitly states the trigger condition ('when asked what the phone number is or whether SMS is set up') and rules out a nearby alternative ('site/SEO settings do not contain it'). It does not disambiguate against the sibling get_communication_settings, which overlaps in subject matter, leaving some routing ambiguity.

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