rybbit-mcp

Live User Count

rybbit_live_users

Read-onlyIdempotent

Retrieve the current number of live or active users on a site in real-time. Provide a site ID to monitor current traffic.

Instructions

Get the current number of live/active users on a site in real-time

Input Schema

TableJSON Schema

Name	Required	Description	Default
`siteId`	Yes	Site ID (numeric ID or domain identifier)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`liveUsers`	Yes	Current live/active user count (normalized from upstream {count} envelope)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.1Sep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "liveUsers": {
+      "description": "Current live/active user count (normalized from upstream {count} envelope)",
+      "type": "number"
+    }
+  },
+  "required": [
+    "liveUsers"
+  ],
+  "type": "object"
+}

First observedv0.5.2Apr 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the freshness semantics ('current', 'real-time'), which is genuine behavioral context beyond the annotations, but it says nothing about return shape or latency despite an output schema existing. Modest added value over structured data.

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?

A single tight sentence with the resource and its real-time nature front-loaded. No filler, no redundancy.

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 one-parameter, read-only metric tool with full schema coverage, an output schema, and annotations covering the safety profile, the description is sufficient to invoke correctly. A brief note on what the count represents (e.g., distinct users in a rolling window) would make it 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?

Only one parameter (siteId) and the schema already documents it fully with 100% coverage, including the numeric-ID-or-domain nuance. The description adds no additional meaning about siteId, so the baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (current number of live/active users) with a real-time qualifier, which cleanly separates it from the sibling rybbit_list_users (which enumerates users rather than counting them). It does not name the sibling explicitly, so it falls just short of a 5.

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

Usage Guidelines3/5

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

The phrase 'in real-time' implies the tool is for live monitoring rather than historical analysis, which is a usable contextual cue. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g., rybbit_list_users or rybbit_get_overview), leaving usage to inference.

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

Deploy Server