Skip to main content
Glama

Besucherzahlen

statistik
Read-only

Die Besucherzahlen dieser Website: Besuche, angesehene Seiten, der Verlauf Tag für Tag und die häufigsten Seiten. Bei JEDER Frage nach Besuchern, Zugriffen oder Reichweite hier nachsehen statt zu schätzen. Gezählt wird nur, was veröffentlicht ist und den Schnipsel trägt (statistik_einbauen). Ein Besuch ist eine Person, die vorbeikommt – nicht jede Seite, die sie ansieht.

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": {
      "website": "<website>"
    },
    "name": "statistik"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
zeitraumNoDie letzten 7, 30 oder 90 Tage. Vorgabe: last30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare read-only, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: only published pages carrying the tracking snippet are counted, and a visit means a person, not every page view. It does not discuss freshness or response shape, so it is not fully exhaustive.

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 what data is available, followed by the usage directive and then the counting caveat. Every sentence contributes useful information with no filler.

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 low-complexity read-only analytics tool, the description, schema, and annotations together give the agent enough to call it correctly. The only notable omission is any note on data freshness or latency.

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 the website identifier and the zeitraum enum are fully documented in the schema. The description adds no syntax or interpretation beyond what the schema already provides.

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 names the specific resource (website visitor statistics) and enumerates the exact metrics: visits, viewed pages, daily trend, and most frequent pages. It implicitly separates this retrieval tool from statistik_einbauen, which sets up tracking.

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?

It explicitly directs the agent to look here for every question about visitors, accesses, or reach instead of estimating. It does not state when not to use the tool, but the intended usage condition is clear.

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