Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Preview link statistics

get_preview_stats
Read-onlyIdempotent

How the site's shared preview link has been viewed: total views, unique visitors, average time spent, and views by design, device, OS and browser, plus when it was last opened, the most-viewed design and the most recent views. Use it to answer "has my client looked at the preview?". Each count is one visit; the site team's own looks are not counted. For the published site's traffic use the site analytics instead.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site to act on
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
Behavior4/5

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

Annotations already declare this is a safe, idempotent, read-only operation, and the description adds meaningful behavioral context: each count is one visit and the site team's own views are excluded. It does not define the reporting time window or behavior when no preview link exists, so it stops short of full transparency.

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?

The description is compact and front-loaded with what the tool returns, followed by a use case, counting semantics, and the relevant alternative. Every sentence adds useful information without repeating the name or schema.

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?

For a read-only statistics tool with complete schema coverage and no output schema, the description is largely complete because it enumerates the returned metrics and clarifies usage. It leaves minor gaps around the reporting period and edge cases such as missing or inactive preview links.

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%, so both site_id and user_goal are already documented in the schema. The description adds no parameter-specific syntax, formatting, or constraints beyond that, making the schema the primary source of parameter semantics.

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?

The description clearly identifies the resource and scope: statistics for how the site's shared preview link has been viewed. It enumerates the specific metrics returned and explicitly distinguishes this from published-site traffic analytics, so an agent can separate it from sibling analytics tools.

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?

It gives a concrete usage scenario: answer "has my client looked at the preview?" and explicitly redirects published-site traffic questions to the site analytics instead. This provides both when-to-use and when-to-use-an-alternative guidance.

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