dendrite-admin-mcp

Purge room

purge_room

Delete a room and all its events from Dendrite's database. Media files are not affected. This action is irreversible.

Instructions

Remove a room and all its events from Dendrite's database. Does not delete associated media. Irreversible.

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": {
      "roomId": "<roomId>"
    },
    "name": "purge_room"
  }
}

Input Schema

Name	Required	Description	Default
`roomId`	Yes	Room ID, e.g. !abc123:example.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses critically important behavior: irreversibility and non-deletion of associated media. This goes beyond a basic mutation description. However, it doesn't mention permission requirements or other potential side effects, so it's not exhaustive but strong.

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 two sentences, front-loaded with the primary action and then essential caveats. Every word earns its place; no fluff or repetition.

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?

For a simple one-parameter tool with no output schema, the description covers all essential aspects: what is removed, what is not removed, and the irreversible nature. This is complete enough for an agent to safely select and invoke the tool.

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 coverage is 100% with roomId already described as 'Room ID, e.g. !abc123:example.com'. The description adds no new parameter-level detail beyond the schema, so the baseline score of 3 is appropriate.

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 action: 'Remove a room and all its events from Dendrite's database.' This is specific with a verb and resource, and it distinguishes purge_room from siblings like evacuate_room, which likely only moves users, not deletes the room. The scope is unambiguous.

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 description implies use for permanent room deletion but does not explicitly state when to use this versus alternatives like evacuate_room. No exclusions or alternative tool names are mentioned, leaving the agent to infer the intended use case.

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

Deploy Server