Skip to main content
Glama

Besucherstatistik einbauen

statistik_einbauen

Baut die Besucherstatistik in die HTML-Seiten des Arbeitsbereichs ein (Zusatzpaket «Statistik»). Der Schnipsel kommt vom Portal – nie selbst einen schreiben, er trägt die Kennung dieser Website. Gibt den Absatz für die Datenschutzerklärung zurück: Der GEHÖRT auf die Seite und ist kein Vorschlag – ohne ihn zählt eine Website ihre Besucher, ohne es zu sagen. Gezählt wird erst nach dem Veröffentlichen. Mit entfernen=true wieder herausnehmen.

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_einbauen"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateienNoNur diese Dateien. Ohne Angabe alle HTML-Dateien. PHP-Seiten fasst das Werkzeug nicht an – dort steht oft eine Vorlage für viele Seiten; den Schnipsel dort von Hand einsetzen.
spracheNoSprache des Datenschutz-Absatzes – die Sprache der WEBSITE, nicht die des Gesprächs. Vorgabe: de.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
entfernenNoDen Schnipsel wieder herausnehmen. Vorgabe: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds substantial context beyond that: which files are modified (HTML, not PHP), that the injected snippet carries the site's identifier, that the returned privacy paragraph is mandatory and must be placed on the page rather than being advisory, and that reporting is delayed until publication. That is exactly the kind of side-effect and lifecycle information annotations cannot express.

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?

Front-loaded with the action and the package prerequisite, then the snippet-source rule, then the return-value obligation, then the removal hint — a sensible order with little waste. The capitalized emphasis ('GEHÖRT') adds tone rather than information, and the privacy sentence is slightly long, but nothing is redundant.

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?

There is no output schema, and the description compensates by explaining that the call returns the privacy-policy paragraph and that it is mandatory — coverage an agent needs to act correctly. It does not describe failure modes (multiple orgs, missing website, PHP-only targets), which are only hinted at in the parameter schema, keeping it just short of fully complete.

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 all four parameters are already documented in the schema. The description only restates the entfernen=true removal behavior and does not add syntax or interaction details (e.g. what happens when dateien lists a non-existent or PHP file). Baseline 3 applies.

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 — inserting the visitor-statistics snippet into the workspace's HTML pages — and names the add-on package it depends on («Statistik»). It is clearly distinct from the sibling 'statistik' (viewing stats) and from file-manipulation siblings, and it names the non-covered case (PHP pages) explicitly.

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?

Gives clear operating context: the snippet must come from the portal and must never be hand-written, counting only begins 'nach dem Veröffentlichen' (pointing at the publish step), and removal is done with entfernen=true. It stops short of explicitly naming alternatives such as the publish or statistik tools, so the agent must infer the workflow step order.

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