Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Run the data retention cleanup now

run_retention_cleanup
Destructive

Apply the site's retention policy immediately (see get_privacy_ops_status for its periods and mode). It does three things: (1) PERMANENTLY purges contacts, submissions and activity whose 14-day recovery window has passed — that cannot be undone; (2) takes submissions and contacts older than the policy allows and, in "delete" mode, deletes them recoverably for 14 days, or, in "anonymize" mode, strips their names, emails and phone numbers in place — which cannot be undone; (3) records the run. Contacts that still have live submissions are kept. Returns the counts.

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

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

Annotations only flag destructiveHint=true; the description goes far beyond by specifying what is permanently purged, the 14-day recovery window, that anonymization is in-place and irreversible, that contacts with live submissions are protected, and that counts are returned. This is exactly the operational context an agent needs before invoking an irreversible tool.

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-loaded with the core action, then a clean numbered breakdown of the three effects. Some phrasing is dense ('in "anonymize" mode, strips their names, emails and phone numbers in place') but each clause conveys distinct risk information.

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?

Despite no output schema, the description states the return content ('Returns the counts') and covers the full behavioral surface of a destructive, non-idempotent operation, so nothing an agent needs before calling is missing.

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 description coverage is 100% and the description adds nothing about site_id or user_goal. Baseline 3 applies since the schema carries all 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 a specific verb and resource ('apply the site's retention policy immediately') and enumerates the three operations performed, which clearly separates it from siblings like get_privacy_ops_status and delete_privacy_data.

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?

The opening tells the agent this is an immediate execution and points to get_privacy_ops_status as the place to learn the policy's periods and mode before/alongside running. It does not explicitly say when *not* to use it or name the narrower delete/restore siblings as alternatives, so it falls short of a 5.

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