Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_audio_settings

Updates a Discord user's audio settings for user or stream contexts, including volume, mute, and soundboard mute.

Instructions

Modify Audio Settings. [PATCH /users/@me/audio-settings/{audio_context_type}/{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": {
      "audio_context_type": "<audio_context_type>",
      "user_id": "<user_id>"
    },
    "name": "modify_audio_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
mutedNomuted
volumeNoVolume 0-1
user_idYesUser ID
soundboard_mutedNosoundboard muted
audio_context_typeYes"user" or "stream"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 safety profile is partly covered. Beyond the bare endpoint path, the description says nothing about required permissions, whether omitted fields are preserved, or how partial updates behave — meaningful gaps for a PATCH mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but it consists almost entirely of a name restatement plus a route string; there is very little content to justify the space saved. Nothing is padded, yet nothing extra is delivered either.

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 five-parameter mutation with no output schema and no coverage of partial-update or permission behavior, the description is too thin. The endpoint path is the only added information an agent could not get from the name and schema.

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 each of the five parameters carries its own description, including the enumeration-style hint of "user" or "stream" for audio_context_type. The description adds no semantics beyond the schema, so the baseline of 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 ("Modify Audio Settings") and appends the raw endpoint PATCH /users/@me/audio-settings/{audio_context_type}/{user_id}. That endpoint does convey the resource scope (per-user, per-audio-context), but there is no verb-plus-resource elaboration that distinguishes it from siblings such as modify_user_settings or modify_current_user_voice_state.

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 tool, when not to, or which sibling handles related settings. An agent must infer from the name alone that this concerns audio-specific settings rather than general user settings.

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