Skip to main content
Glama
Sign In
Discord Server Setup MCP

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_guilds

Discover available Discord servers that the bot can access before performing setup operations.

Instructions

Lists all Discord servers (guilds) that the bot has access to. Use this to discover available servers before performing operations.

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_guilds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/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. It states the tool lists guilds but doesn't disclose behavioral traits like pagination, rate limits, permissions needed, or return format. However, it adds useful context about the purpose (discovery).

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 sentences, front-loaded with the core purpose, followed by usage guidance. Every sentence earns its place with no wasted words, making it efficient and easy to parse.

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?

Given no annotations, no output schema, and 0 parameters, the description is complete for a simple list operation but lacks details on behavioral aspects like return format or limitations. It's adequate but has clear gaps in transparency.

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?

The tool has 0 parameters, and schema description coverage is 100%. The description doesn't need to add parameter semantics, so baseline is 4. It appropriately focuses on tool purpose rather than parameters.

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 specific action ('Lists all Discord servers') and resource ('guilds'), with explicit scope ('that the bot has access to'). It distinguishes from siblings like 'get_guild_info' (detailed info for one guild) and 'select_guild' (choose a specific guild).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool: 'Use this to discover available servers before performing operations.' This provides clear context for usage versus alternatives like 'get_guild_info' (for details on a known guild) or 'select_guild' (to choose one).

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