discord-server-mcp

list_templates

Read-only

Lists built-in server templates for apply_blueprint so you can choose a starting layout before configuring a Discord server.

Instructions

List the built-in server templates for apply_blueprint.

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": "list_templates"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Use this bot (name or id) instead of choosing automatically

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the templates are built-in and feed apply_blueprint, which is genuine workflow context, but it says nothing about return shape, number of templates, or whether templates are per-server or global.

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?

One sentence, no filler, and the resource and its purpose are stated up front. Nothing could be removed without losing information.

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 trivial one-parameter read tool this is close to adequate, but with no output schema the description should say what identifiers a template exposes so the agent knows what to pass to apply_blueprint. The unexplained bot parameter on a template-listing call is left dangling.

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 single parameter has 100% schema description coverage ("Use this bot (name or id) instead of choosing automatically"), so the baseline is 3. The description does not touch the bot parameter at all, and does not explain why a bot selector matters when listing built-in templates.

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?

A specific verb ("List") plus a specific resource ("built-in server templates"), and it names the consuming tool apply_blueprint so the agent can place it in a workflow. It distinguishes itself from the other list_* siblings by scoping to templates, though it never says what a template actually contains.

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?

Mentioning apply_blueprint implies the use case (discover templates before applying one), but there is no explicit when-to-use, no when-not, and no mention of alternatives or prerequisites. Usage is inferred rather than stated.

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