Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_current_user_voice_state

Update your voice state in a Discord stage channel to request to speak or switch between speaker and audience roles.

Instructions

Your voice state in a stage channel: request to speak, or become speaker/audience. [PATCH /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": "modify_current_user_voice_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
suppressNoSuppressed (audience) in a stage
channel_idNoChannel ID
request_to_speak_timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the bracketed PATCH endpoint confirms this is a mutation. The description adds the stage-channel context and the hand-raise/audience semantics, but omits permission requirements (suppressing another user's/your own stage state typically needs elevated permissions) and any note on what state changes take effect or are reversible.

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?

A single front-loaded sentence states scope and supported actions, with the HTTP route appended as a compact technical anchor. No filler, though the phrasing is slightly telegraphic.

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 non-destructive mutation tool with annotations and no output schema, the description is largely sufficient but leaves gaps: it never clarifies that channel_id/guild_id identify the stage, nor whether the tool works outside stage channels, and it says nothing about permission or error conditions.

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?

Schema coverage is already 80%, so the schema documents the parameters well. The description nonetheless adds intent mapping: 'request to speak' corresponds to request_to_speak_timestamp and 'become speaker/audience' to the suppress flag, which helps an agent choose parameters rather than just read their types.

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 names a concrete resource ('your voice state in a stage channel') and enumerates the operations it supports (request to speak, become speaker/audience), plus the underlying PATCH endpoint for precision. The possessive 'Your' distinguishes it from the sibling modify_user_voice_state, though that sibling is not named explicitly.

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

Usage Guidelines3/5

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

The three supported actions imply when to call it (raising a hand, switching to audience/speaker), but there is no explicit statement of prerequisites, alternatives, or when-not-to-use. An agent must infer that modify_user_voice_state is the tool for other members.

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