Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_voice_regions

Read-only

Retrieve available voice regions for a Discord server by guild ID, helping you identify region options before configuring voice channels or deployments.

Instructions

List Guild Voice Regions. [GET /guilds/{guild_id}/regions]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "list_guild_voice_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description contributes the REST route, which confirms this is a thin passthrough to GET /guilds/{guild_id}/regions with no side effects, but says nothing about pagination, rate limits, or what a region record contains.

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 compact, front-loaded fragments with zero filler; the resource name leads and the endpoint follows as supporting detail. 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 single-parameter read, the essentials are present and annotations cover safety. However, with no output schema, the description does not state that the return is a list of voice-region objects (id/name/optimal flags), leaving the agent to guess the response shape.

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 coverage is 100% for the single guild_id parameter ("Server (guild) ID"), so the schema already carries the full parameter meaning. The description adds nothing about the ID's format or source beyond the endpoint template, which merely mirrors the schema.

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?

The description gives a specific verb+resource ("List Guild Voice Regions") plus the backing REST endpoint, so the agent knows this is a read of a guild's available voice regions. It does not differentiate against the sibling list_voice_regions (sounds like the non-guild, global variant), so the sibling distinction is left to inference.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus list_voice_regions or any other sibling, and no preconditions such as requiring a guild context or the bot being a member. The endpoint notation implies usage but never states it.

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