Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Visits by channel, page and device

webops_visits
Read-onlyIdempotent

Analytics for a connected website, a window against the one before: visits, engagement and conversions; by channel (with weekly series), landing page and device; conversions by event and page. Later pages of a visit are not held. 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_visits"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow length in whole weeks of days (7, 14, … 182; default 28), ending on the latest day with data, against the same number of days before.
pageNoOne page, exactly as webops_pages returns it.
limitNoHow many landing pages and converting pages (default 10).
deviceNodesktop, mobile or tablet.
domainYes
channelNoAn Analytics channel, e.g. Organic Search, Direct.
after_toNoLast day of the later window (same length as the earlier one).
before_toNoLast day of the earlier window.
after_fromNoFirst day of the later window.
before_fromNoInstead of days: first day of the earlier window (give all four).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety needs no restating (the trailing "Read-only" is redundant). The description earns credit for non-obvious context the annotations cannot convey: comparison is against an equal-length prior window, later pages of a visit are excluded so visit depth is truncated, and requests for another organization's or an unconnected site return not found.

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?

Very short and front-loaded with the outcome, then the breakdowns, then constraints. The clipped, fragmentary phrasing ("Another organization's or an unconnected site answers not found") costs a little readability, and "Read-only" duplicates the annotation.

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 10-parameter, no-output-schema analytics tool, the description covers the metric families returned, the comparison model, a data-coverage limitation and error behavior. What remains thin is the exact response shape and how the week-aligned days parameter overrides the explicit date parameters.

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 90%, so the schema already explains days, page, limit, device, channel and the four explicit date bounds. The description adds only loose hints (channel includes a weekly series; conversions are broken down by event and page) rather than clarifying how days and the *_from/*_to pairs interact.

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?

States a concrete verb+resource: website analytics of visits, engagement and conversions, broken out by channel, landing page and device, with a comparison window. That is far more specific than the title, though it never names which sibling (webops_breakdown, webops_compare, webops_daily) an agent should prefer for narrower cuts.

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

Usage Guidelines3/5

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

The period-over-period framing ("a window against the one before") implies when this tool fits, and the "not found" note gives a negative precondition. But there is no explicit when-not guidance and no routing to alternative tools for single-period or channel-only queries.

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