Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Live User Count

rybbit_live_users
Read-onlyIdempotent

Monitor real-time active user counts on websites to track engagement and performance metrics.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)

Implementation Reference

  • The handler function that executes the "rybbit_live_users" tool by calling the Rybbit client API.
    async (args) => {
      try {
        const count = await client.get<number>(
          `/sites/${args.siteId}/live-user-count`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: truncateResponse({ liveUsers: count }),
            },
          ],
        };
      } catch (err) {
        const message = err instanceof Error ? err.message : String(err);
        return {
          content: [{ type: "text" as const, text: `Error: ${message}` }],
          isError: true,
        };
      }
  • The MCP registration of the "rybbit_live_users" tool.
    server.registerTool(
      "rybbit_live_users",
      {
        title: "Live User Count",
        description:
          "Get the current number of live/active users on a site in real-time",
        inputSchema: {
          siteId: siteIdSchema,
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
      },
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the 'real-time' behavioral trait not captured in annotations, indicating data freshness. However, it omits specifics about what defines a 'live' user (e.g., active in last 5 minutes) or potential latency constraints.

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?

The description is a single, efficient sentence that immediately conveys the tool's purpose. It is appropriately front-loaded with the action verb 'Get' and contains no redundant or filler text. Every word serves to clarify scope ('current', 'live/active', 'real-time', 'on a site').

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?

Given the tool's simplicity (single required parameter, read-only operation, clear annotations), the description is sufficient. It compensates for the missing output schema by indicating a numeric return ('number of... users'). For a real-time counter, it adequately covers necessary context without over-specifying.

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?

With 100% schema description coverage, the input parameter siteId is fully documented in the schema as 'Site ID (numeric ID or domain identifier)'. The description references 'on a site' which aligns with the parameter but adds no additional semantic detail, syntax examples, or format guidance beyond the schema.

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?

The description clearly states the tool retrieves a 'current number of live/active users' with 'real-time' specificity. The 'live/active' and 'number' phrasing effectively distinguishes this from sibling list/get operations like rybbit_list_users by indicating it returns a count rather than detailed records.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like rybbit_get_metric or rybbit_list_users. It mentions 'real-time' implying current data needs, but lacks explicit when/when-not conditions, prerequisites, or rate limit warnings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nks-hub/rybbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server