Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

Get a realtime traffic snapshot

websiteAnalytics_realtime_get
Read-onlyIdempotent

Returns a compact snapshot of traffic over Umami's trailing 30-minute realtime window: total page views, distinct visitors, tracked custom events, and distinct countries, plus the snapshot timestamp. The visitor total is not directly comparable to the removed active endpoint's five-minute count. Use it to see recent activity; use the query endpoint for historical ranges. Requires a plan that includes analytics (403 otherwise); all-zero totals until the website is published and has traffic.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "websiteAnalytics_realtime_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: the 403 plan-gating failure mode, the all-zero-until-published caveat, and the warning that visitor totals are not comparable to the removed `active` endpoint's five-minute count. That last note prevents a real misinterpretation an agent could otherwise make.

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 dense sentences with the payload description front-loaded, followed by the routing rule and then the preconditions. Nothing is redundant with the schema or annotations, and the migration caveat about the removed `active` endpoint earns its space.

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?

With no output schema, the description carries the return-value burden and does so by naming every field in the snapshot plus the timestamp. Combined with the window definition, failure mode, and empty-state behavior, an agent has everything needed to call this and interpret the result.

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?

There is one required parameter (websiteId) with 0% schema description coverage, and the description never mentions it or its format. The name is largely self-explanatory and the description establishes that the tool is website-scoped, but it does not compensate for the documentation gap.

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 ("Returns a compact snapshot of traffic") and pins the exact scope: Umami's trailing 30-minute realtime window. It enumerates the returned metrics (page views, visitors, custom events, countries, timestamp), so an agent knows precisely what this yields versus the historical query endpoint.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Use it to see recent activity; use the query endpoint for historical ranges," naming the sibling and the condition that selects it. It also adds two preconditions (plan must include analytics, 403 otherwise; all-zero totals until the site is published and has traffic) that determine when results are meaningful.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cactal toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources