Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_voice_channel_status

Set or clear the status text displayed under a Discord voice channel, letting you show a short message to everyone who joins that channel.

Instructions

Set the status text shown under a voice channel. [PUT /channels/{channel_id}/voice-status]

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": {
      "channel_id": "<channel_id>"
    },
    "name": "set_voice_channel_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered structurally. The description adds nothing beyond the endpoint path — it does not say whether the user must be connected to the voice channel, whether the status is scoped per-guild or global, or how clearing behaves (that detail lives only in the schema).

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?

One sentence plus a bracketed REST endpoint mapping, front-loaded with the action and zero filler. The endpoint notation is mildly redundant but useful for agents reasoning in API terms.

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?

For a mutation tool with no output schema and only half-annotated parameters, the description should carry more. It omits permissions requirements, the voice-connection prerequisite, and any hint of the response, leaving the agent to guess at operational context beyond the endpoint path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the description contributes zero parameter meaning — no mention of the required channel_id, the status string, or the null-clears behavior that the schema documents. An agent reading only the description would not know a channel identifier is mandatory or that status is optional.

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?

States a specific verb and resource ("Set the status text shown under a voice channel"), and the phrase "under a voice channel" distinguishes it from the sibling set_custom_status / set_status tools. It stops short of naming those siblings explicitly, so an agent must infer the boundary itself.

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, when-not-to-use, or prerequisite guidance. With siblings like set_custom_status and modify_current_user_voice_state present, the definition offers nothing to help an agent choose between them, leaving routing entirely to inference from the name.

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