Skip to main content
Glama
Sign In
Discord Server Setup MCP

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

preview_template

Preview a Discord server template to see its roles, categories, and channels before applying it.

Instructions

Shows detailed information about a specific template including all roles, categories, and channels.

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": {
      "templateId": "<templateId>"
    },
    "name": "preview_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesTemplate ID to preview (gaming, community, business, study-group)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / templateId / description
      Previous value: -"Template ID to preview"New value: +"Template ID to preview (gaming, community, business, study-group)"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so description carries full burden. It states output content but omits traits like read-only nature, authentication needs, or absence of side effects. Adequate but not comprehensive.

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 with no redundancy. Front-loaded with verb and object. Efficient.

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?

Simple tool with one parameter and 100% schema coverage. Description covers what the tool returns. Minor omission: no mention of behavior if template not found.

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 already provides 100% coverage with examples. Description adds context about return content but not extra parameter meaning. Baseline 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?

Description clearly states the tool shows detailed information about a specific template, listing included components (roles, categories, channels). It distinguishes from siblings like list_templates and apply_template.

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?

Usage is implied (when you need template details) but no explicit when-to-use, when-not-to-use, or alternative tools mentioned. Context from sibling tools partially fills gap.

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