Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_voice_regions

Read-only

Retrieves the voice regions available for Discord calls and voice channels, so you can choose a region when configuring or troubleshooting voice connectivity.

Instructions

Voice regions available for calls/channels. [GET /voice/regions]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The text adds only the REST endpoint mapping ([GET /voice/regions]), which is mildly useful for cross-referencing API docs but discloses nothing about the returned set's size or stability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments, front-loaded with the resource and followed by the endpoint tag, with no filler. It is efficient, though the terseness contributes to the missing sibling differentiation rather than compensating for it.

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?

With no output schema, the description should clarify what a 'voice region' entry contains, and it does not. For a zero-parameter read tool this is a modest gap, but the ambiguity with list_guild_voice_regions leaves an agent without enough information to choose confidently.

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 takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly implies an unfiltered list with nothing to configure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (voice regions) and scope (available for calls/channels), which is more than a tautology. However, it does not distinguish itself from the sibling list_guild_voice_regions, so an agent cannot tell from the description whether this returns global regions or guild-specific ones.

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 when-to-use guidance and no mention of alternatives, despite a closely named sibling (list_guild_voice_regions) that an agent could easily confuse with this one. The reader must infer the use case from the name alone.

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