dendrite-admin-mcp

Create a registration token

create_registration_token

Create registration tokens to gate new-account signups. Generate a random token automatically or specify a custom token with length, expiry, and usage limits.

Instructions

Create a new registration token that can be used to gate new-account registration. Omit 'token' to have Dendrite generate a random one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_registration_token"
  }
}

Input Schema

Name	Required	Description
`token`	No	Explicit token value; random if omitted
`length`	No	Length of a randomly generated token
`expiryTime`	No	Unix ms timestamp after which the token is invalid
`usesAllowed`	No	Maximum number of times this token can be used

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.1/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 the full burden for behavioral disclosure. It does reveal a key behavior: omitting 'token' triggers random generation. However, it does not mention permissions, side effects, or return value, which are relevant for a create operation. This is adequate but not rich.

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?

Two concise sentences deliver the purpose and key usage guidance without waste. The most important information is front-loaded, making it easy to scan.

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?

For a create tool with no output schema and no annotations, the description gives the core purpose and generation behavior but omits what the response looks like, whether there are permission requirements, or how this integrates with other token operations. While not incomplete enough to be unusable, it leaves some contextual gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds semantic value by explaining the relationship between omission of the 'token' parameter and random generation, which is beyond what the schema explicitly states. This elevates it to a 4.

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 starts with 'Create a new registration token', giving a specific verb and resource. It further clarifies the token's purpose ('gate new-account registration'), which distinguishes it from sibling tools like list/get/update/delete_registration_token.

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 clear context: this tool is for creating tokens to gate registration. It also gives a usage hint about omitting 'token' to generate a random one. However, it does not explicitly mention when to use this tool over alternative sibling tools or any exclusions, so it stops short of a full 5.

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

Deploy Server