Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Who visits and what they do on a page

webops_visitors
Read-onlyIdempotent

Over the analysis window: visits, engagement and conversions by browser, system and device; by country, language and new or returning; by source, medium and campaign, with referral sites; clicks out (sites) and downloads (files) by page; how far pages are read. Another organization's or an unconnected site answers not found. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "webops_visitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many in each list, most visits first (default 10).
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description merely restates structured data. What it adds beyond annotations is the scoping behavior — cross-organization or unconnected domains return 'not found' — but it never says what the analysis window is, how results are grouped, or how the lists are ordered/truncated.

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?

Four compact clauses, no filler, and the metric inventory is front-loaded. The opening is a fragment ('Over the analysis window:') that delays the subject slightly, and the dimension list is dense enough to read as a data dictionary rather than prose, but nothing is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of conveying the return shape, and it does list the reported dimensions well. It leaves gaps that matter for a 2-parameter reporting tool: the default analysis window is never defined, whether results come back as separate ranked lists per dimension is only implied, and the required 'domain' argument is never mentioned.

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 50%: 'limit' is documented in the schema (count per list, most visits first, default 10) while 'domain' has only a pattern and length constraints. The description compensates partially by implying per-list outputs ('how many in each list'), which explains what limit applies to, but it never explains that 'domain' identifies the site to analyze or where to obtain a valid value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly which metrics and breakdowns the tool returns (browser/system/device, country/language/new-vs-returning, source/medium/campaign with referrals, outbound clicks, downloads, read depth), which is far more specific than the title alone. It stops short of naming a sibling it is not (webops_visits, webops_breakdown, webops_daily all sound adjacent), so an agent cannot fully disambiguate from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool versus the many breakdown/visits siblings, and no prerequisites such as needing a connected site or a known domain. The only conditional guidance is the negative case: another organization's or an unconnected site answers 'not found'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources