Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user_voice_state

Read-only

Fetches a user's current voice state in a Discord server to check voice channel membership, mute, and deafen status using the guild ID and user ID.

Instructions

Get User Voice State. [GET /guilds/{guild_id}/voice-states/{user_id}]

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>",
      "user_id": "<user_id>"
    },
    "name": "get_user_voice_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 covered. Beyond that the description only reveals the underlying REST route; it does not disclose permission requirements, error behavior (e.g. user not connected to voice), or what the voice state contains.

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 with no filler; the name and route are front-loaded. It is terse rather than padded, though the terseness borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple two-parameter read with no output schema, so the description should describe what a 'voice state' includes (channel, mute/deaf flags, session) and when the lookup fails. Neither is present, leaving the agent unable to anticipate the return value or error conditions.

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 100% for both guild_id and user_id, so the baseline is 3. The endpoint template merely maps the two parameters into a path and adds no format, permission, or ID-type nuance beyond the schema.

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?

The text 'Get User Voice State' essentially restates the tool name, but the appended endpoint '[GET /guilds/{guild_id}/voice-states/{user_id}]' adds real scope information: the state is per-guild and per-user. It never distinguishes this from the sibling 'get_current_user_voice_state', which is the obvious confusion risk.

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, no prerequisites, and no mention of the closely named alternative get_current_user_voice_state. An agent must infer from the endpoint path alone that this reads another user's state rather than its own.

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