@lodd/mcp-server

get_realtime

Retrieve the count of active visitors on a site within the last 5 minutes.

Instructions

Get the number of currently active visitors on a site (visitors with activity in the last 5 minutes)

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": "get_realtime"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Site domain or UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Discloses the definition of 'active' (activity in last 5 minutes), which is crucial. No annotations provided, so description carries burden; it adequately covers behavioral expectations for a read-only operation.

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?

Single sentence, front-loaded, no redundancy; every word earns its place.

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?

Complete for a simple tool: explains output (count) and key context (5-minute window). No output schema needed; description suffices.

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?

Single parameter 'site' is fully described in schema (100% coverage). Description adds no additional meaning beyond 'Site domain or UUID'.

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?

Clearly states the action ('Get'), resource ('number of currently active visitors'), and context ('in the last 5 minutes'), distinguishing it from historical analytics tools.

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?

Implicitly indicates real-time use case, but does not explicitly contrast with siblings like get_analytics or get_timeseries; context is clear enough.

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