Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_voice_members

Read-only

Shows who is currently in a Discord server's voice channels, optionally one channel, with mute, deafen, and stream flags plus your own connection location.

Instructions

Who is in voice channels of a server right now (optionally one channel), with mute/deafen/stream flags. Also shows where you are connected.

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

Input Schema

NameRequiredDescriptionDefault
guild_idYes
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. The description adds real value beyond that by disclosing the response is a live snapshot ('right now'), that it can report mute/deafen/stream state, and that it also surfaces the caller's own connection. It omits visibility/permission requirements and whether bots are included, which keeps it at 3 rather than higher.

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 short sentences, both front-loaded with the most decision-relevant information (scope and live-ness first, returned fields second). No filler, hedging, or repetition.

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?

For a read-only, two-parameter query with no output schema, the description covers the core return contents and the real-time nature well enough to call it correctly. Missing pieces like permission prerequisites and whether results are paginated are minor for this tool 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 description coverage is 0%, so the description carries weight, and it does clarify that the required guild_id means 'server' and that channel_id is an optional single-channel filter. However, it never states the ID format (snowflake vs name) or what happens if channel_id names a non-voice channel, leaving a real gap for two undocumented parameters.

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 resource ('who is in voice channels of a server') plus a real-time qualifier ('right now') and names the payload fields ('mute/deafen/stream flags'), which separates it from generic member listings like list_guild_members. It stops short of explicitly naming a sibling to contrast with, so it lands at clear-but-not-differentiated-from-alternatives.

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 explicit when-to-use or when-not-to-use guidance and no alternative named. The parenthetical '(optionally one channel)' hints at scoping but is a parameter note, not usage guidance, so an agent gets only implied direction.

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