discord-mcp

voice_get_current_user_state

Read-onlyIdempotent

Retrieve the bot's current voice state in a Discord guild, including channel, mute/deaf flags, and request-to-speak timestamp.

Instructions

Purpose: Fetch the bot's own voice state in a guild (/guilds/{guild.id}/voice-states/@me).

Returns: voice state shape (channel, mute/deaf flags, request_to_speak_timestamp).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild to query

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "channel_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "deaf": {
-        "type": "boolean"
-      },
-      "guild_id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "mute": {
-        "type": "boolean"
-      },
-      "request_to_speak_timestamp": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "self_deaf": {
-        "type": "boolean"
-      },
-      "self_mute": {
-        "type": "boolean"
-      },
-      "self_stream": {
-        "type": "boolean"
-      },
-      "self_video": {
-        "type": "boolean"
-      },
-      "session_id": {
-        "type": "string"
-      },
-      "suppress": {
-        "type": "boolean"
-      },
-      "user_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "guild_id",
-      "channel_id",
-      "user_id",
-      "session_id",
-      "deaf",
-      "mute",
-      "self_deaf",
-      "self_mute",
-      "self_video",
-      "suppress",
-      "request_to_speak_timestamp"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "channel_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deaf": {
+        "type": "boolean"
+      },
+      "guild_id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "mute": {
+        "type": "boolean"
+      },
+      "request_to_speak_timestamp": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "self_deaf": {
+        "type": "boolean"
+      },
+      "self_mute": {
+        "type": "boolean"
+      },
+      "self_stream": {
+        "type": "boolean"
+      },
+      "self_video": {
+        "type": "boolean"
+      },
+      "session_id": {
+        "type": "string"
+      },
+      "suppress": {
+        "type": "boolean"
+      },
+      "user_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "guild_id",
+      "channel_id",
+      "user_id",
+      "session_id",
+      "deaf",
+      "mute",
+      "self_deaf",
+      "self_mute",
+      "self_video",
+      "suppress",
+      "request_to_speak_timestamp"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the concrete endpoint and the returned voice-state fields, offering a bit of extra context without detailing error cases or authorization requirements.

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?

The description is two short, focused sections: Purpose and Returns. Every sentence carries information, the main purpose is front-loaded, and there is no filler or unnecessary 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?

Given the tool's simplicity, a single required guild_id parameter, rich annotations, and an existing output schema, the description covers what an agent needs to understand the tool's role and return shape. It could have explicitly contrasted itself with voice_get_user_state, but that is not essential for making the call.

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%, with guild_id documented as 'Guild to query' and a regex pattern for its format. The description adds no additional meaning about the parameter beyond showing it in the endpoint path, so the baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb ('Fetch') and a specific resource: the bot's own voice state in a specific guild, with the exact endpoint. It also distinguishes itself from the likely-similar sibling voice_get_user_state by explicitly scoping to the bot's own state rather than any user's state.

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

Usage Guidelines4/5

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

The description makes the intended use clear through 'the bot's own voice state' and the `/guilds/{guild.id}/voice-states/@me` endpoint, implicitly separating it from user-voice-state sibling tools. It does not explicitly name alternatives or state when not to use it, so it falls just short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server