dendrite-admin-mcp

Look up a user's sessions

whois

Retrieve a user's active session and connection information from Dendrite by supplying the user's ID.

Instructions

Retrieve connection/session information Dendrite holds about a given user.

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": {
      "userId": "<userId>"
    },
    "name": "whois"
  }
}

Input Schema

Name	Required	Description	Default
`userId`	Yes	Fully-qualified user ID, e.g. @alice:example.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It indicates a non-destructive read operation ('Retrieve') but does not disclose error behavior, whether multiple sessions are returned, or any side effects. Since the description merely restates the title with a bit more specificity, it adds limited 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?

The description is a single sentence that is concise and front-loaded, containing no filler. It efficiently conveys the tool's purpose without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description gives the basic purpose but does not explain the return value format or any potential edge cases. Since there is no output schema, the description should provide more clarity on what 'connection/session information' entails, making it slightly incomplete.

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?

The schema has full coverage of the single parameter 'userId' with a clear description. The tool description adds no additional meaning beyond what the schema already provides, so the baseline of 3 applies.

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?

The description clearly states the tool retrieves connection/session information for a given user, using a specific verb and resource. It distinguishes itself from sibling tools, which focus on tokens, room management, and user administration, by targeting session data.

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?

The description implies when to use this tool (to look up a user's sessions) but does not explicitly mention alternatives or exclusions. Given the sibling tools, the context is clear enough that this is the session lookup tool, but it lacks explicit 'use when' or 'not for' guidance.

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

Deploy Server