rybbit-mcp

User Detail

rybbit_get_user

Read-onlyIdempotent

Retrieve a user's traits, session history, and activity summary by site ID and user ID to analyze individual behavior.

Instructions

Get detailed information about a specific user including their traits, session history, and activity summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`siteId`	Yes	Site ID (numeric ID or domain identifier)
`userId`	Yes	User ID (identified_user_id or internal user ID)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	User detail payload

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": {
+    "data": {
+      "description": "User detail payload"
+    }
+  },
+  "type": "object"
+}

First observedv0.5.2Apr 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the categories of data returned, but since an output schema exists this is marginal added value rather than deep behavioral context.

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 efficiently written sentence that front-loads the operation and the resource. Every clause earns its place by enumerating the returned content without padding.

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 two-parameter read tool with a rich output schema and full annotation coverage, the definition supplies enough to call it correctly. The only meaningful gap is routing guidance against overlapping user-detail siblings, which is minor given the low complexity.

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% and both parameters (siteId, userId) are documented in the schema, including alternate identifier forms. The description adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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 and resource ('Get detailed information about a specific user') and names the content returned (traits, session history, activity summary). It implicitly distinguishes from list_users by requiring a specific user, but does not differentiate from siblings like rybbit_get_user_traits or rybbit_list_sessions that cover overlapping slices.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternative tools such as get_user_traits or get_session. The name implies a detail lookup, but nothing routes the agent among the many user-related siblings.

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

Deploy Server