Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_current_user_voice_state

Read-only

Retrieve the current user's voice state in a Discord guild by guild ID to inspect voice channel, mute, and deaf status.

Instructions

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

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": "get_current_user_voice_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), so the bar is lower, but the description adds nothing beyond the raw endpoint. It does not say what a voice state contains, what happens for a user not connected to voice, or any error/permission conditions.

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, front-loaded fragments with no wasted prose. The bracketed endpoint is the only added value and is inexpensive to include.

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 simple read-only one-parameter tool this is minimally adequate, but with no output schema the description could state what fields a voice state returns (channel, mute/deaf flags, etc.) or how the 'not in voice' case is represented, which the agent currently cannot know.

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% and the single guild_id parameter is documented in the schema itself, so the description neither needs nor provides extra parameter detail. Baseline 3 applies.

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 description restates the tool name and appends the HTTP endpoint, which confirms it fetches the calling user's own voice state in a given guild (the @me path segment is mildly informative). It does not distinguish itself from the sibling get_user_voice_state, which presumably fetches another user's state, so the agent gets no explicit contrast.

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 get_user_voice_state, modify_current_user_voice_state, or list_voice_members. The @me endpoint implicitly signals 'self only', but the agent must infer that rather than being told.

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