Skip to main content
Glama

visitor_stats

See which visitor families (AI crawlers, search engines, browsers) hit the site recently.

Read-only aggregate counters: per-family hit totals plus trap-page hits. No IPs or raw User-Agents are returned — only family labels and counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "visitor_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days. Range 1-90; default 7.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days. Range 1-90; default 7."
    • addedInput schema / properties / days / maximum
      Added value: +90
    • addedInput schema / properties / days / minimum
      Added value: +1
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it declares the operation read-only, states the output is aggregated, and explicitly enumerates what is NOT returned (IPs, raw User-Agents). What is missing is minor — no mention of auth requirements, rate limits, or whether zero-traffic windows return empty results.

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, front-loaded with the purpose and followed by the behavioral constraints. Every sentence contributes new information with no repetition of the tool name or restatement of structured fields.

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?

For a single-parameter read-only stats tool with an output schema present, the definition covers purpose, response content (family labels and counts plus trap-page hits), and privacy boundaries. Nothing an agent needs to decide or call it correctly is absent.

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% and the sole 'days' parameter is fully documented in the schema (range 1-90, default 7), so the baseline of 3 applies. The description adds nothing about the look-back window or what 'recently' means numerically.

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 and resource: which visitor families (AI crawlers, search engines, browsers) hit the site recently, plus the aggregate counters returned. The scope is narrow enough that an agent could distinguish it from any raw-log or per-IP analytics tool without opening the schema.

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

Usage Guidelines4/5

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

The description sets clear context ('recently', aggregate counters, read-only) and implicitly scopes usage to traffic-composition questions rather than per-visitor investigation, reinforced by 'No IPs or raw User-Agents are returned'. It stops short of naming a when-not-to-use condition or a specific alternative, but none of the sibling tools are close substitutes.

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