Skip to main content
Glama

site_stats

Read-only

Visitor statistics for a site: page views and unique visitors per day, top pages, referring sites and pages, visitors by country and which location served them. Counted without cookies or tracking scripts; recent views can take about a minute to appear.

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": {
      "site": "<site>"
    },
    "name": "site_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, including today (default 7, max 90).
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavioral traits: data is collected without cookies or tracking scripts, and recent views may take about a minute to appear — a latency caveat an agent would otherwise misread as missing data. It stops short of noting retention limits despite the 90-day cap on the days parameter.

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?

Two sentences, front-loaded with what is returned, then the freshness caveat. Every clause carries information: metric list, counting method, and latency. No filler or restatement of the tool name.

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?

With no output schema, the description correctly enumerates the result categories so the agent knows what comes back, and the freshness note covers the main behavioral surprise. The one real gap is the identity of the required 'site' argument, which is undocumented in both the schema and the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the days parameter is fully documented in the schema, but the required 'site' parameter has no description at all, and the description does not clarify whether it expects a domain name, a site ID, or a handle. With coverage this low, the description should compensate for the undocumented required parameter but does not.

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+resource (visitor statistics for a site) and enumerates the concrete metrics returned: daily page views and unique visitors, top pages, referrers, and country/location breakdowns. No sibling tool covers analytics, so it is trivially distinguishable from the domain, file, and repo tools in the list.

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 description implies usage (check a site's traffic) but gives no explicit when-to-use framing, no prerequisites, and no pointer to sibling tools such as list_sites for discovering a valid site identifier. An agent must infer that this is a reporting call rather than an administrative one.

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