Skip to main content
Glama
Sign In
dendrite-admin-mcp

dendrite-admin-mcp

by niels-emmer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Download room state from a remote server

download_room_state

Fetch the room state for a given room from a specific federated server to debug state resolution and federation issues.

Instructions

Fetch and return the room state for a given room as seen by a specific federated server. Useful for debugging state resolution and federation issues.

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

Input Schema

NameRequiredDescriptionDefault
roomIdYesRoom ID, e.g. !abc123:example.com
serverNameYesServer name to query, e.g. matrix.org

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. The verb 'Fetch and return' implies a read-only operation, but it does not explicitly state that no changes are made, whether it requires special permissions, or any potential side effects (e.g., network calls, latency). It is adequate but not transparent about behavioral nuances beyond the obvious read.

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 main action, and includes a concise use case. Every sentence earns its place with no wasted words.

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?

The tool has only 2 parameters, no output schema, and no annotations. The description covers the purpose, the object being fetched, and the typical use case (debugging). It lacks a note on the return format, but for a tool that simply fetches state, the description is largely adequate. Slightly more could be said about response structure, but it is not critically 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?

Schema description coverage is 100%: both parameters (roomId, serverName) are fully described with examples in the schema. The description adds no additional parameter semantics beyond the schema, 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 'Fetch and return the room state for a given room as seen by a specific federated server.' It uses specific verb and resource ('room state'), and distinguishes itself from all sibling tools, which are about tokens, user admin, or room management actions like purge/evacuate.

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 provides usage context: 'Useful for debugging state resolution and federation issues.' This clearly implies when to use it, but it does not explicitly contrast with alternatives or state exclusions. Since no sibling tool serves a similar purpose, this is sufficiently clear.

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

Deploy Server

Other Tools