Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Turn off site analytics

disable_analytics
DestructiveIdempotent

Stop the site's built-in visitor analytics. By default only collection stops and the connection is kept, so enable_analytics later resumes the same history. delete_history: true also deletes the site's analytics collection itself — permanent: past reports can no longer be read, and re-enabling starts from nothing. Use it only when the owner explicitly asks to delete their analytics history.

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.
delete_historyNoAlso permanently delete the collected analytics history (default false)

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

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

Annotations already flag destructiveHint/idempotent, but the description goes well beyond: default behavior preserves the connection so enable_analytics resumes history, while delete_history destroys past reports irrecoverably and resets the site to a blank slate. That is exactly the consequence detail an agent needs before a destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what happens by default, what the flag changes and what it costs, then the permission gate. Default behavior is front-loaded before the destructive option, which is the right ordering for a risky mutation.

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?

No output schema exists, but for a boolean-flag mutation tool the description supplies the default path, the destructive path's irreversibility, the recovery story via the sibling tool, and the consent prerequisite. Nothing material is left for the agent to guess.

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; the description earns an extra point by adding consequence semantics the schema only gestures at — "past reports can no longer be read, and re-enabling starts from nothing" — plus the default-false implication made explicit. site_id and user_goal get no added meaning, keeping it off a 5.

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?

Opens with a specific verb+resource: "Stop the site's built-in visitor analytics." It distinguishes itself from the sibling enable_analytics by naming it and describing how the two interact (resuming the same history).

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?

Explicitly states the condition that distinguishes the two modes (default = stop collection only; delete_history = permanent deletion) and gives a clear gating rule: "Use it only when the owner explicitly asks to delete their analytics history." Both when-to-use and when-not-to-use are covered.

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