Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_call

Change the voice region for a Discord DM or group call by providing the channel ID and desired region.

Instructions

Change the voice region of a DM/group call. [PATCH /channels/{channel_id}/call]

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

Input Schema

NameRequiredDescriptionDefault
regionNoVoice region id
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive mutation, so the description only needs added context. It confirms the mutation is limited to voice region, but says nothing about required permissions or what happens to an in-progress call when the region changes — a meaningful gap for a live-call mutation.

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?

One sentence plus the endpoint reference, with the resource scope front-loaded and no filler. Every element contributes to identifying the operation.

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?

For a two-parameter tool with full schema documentation and annotations, the description covers scope and endpoint adequately. The main shortfall is not clarifying side effects on an active call or permission requirements.

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 both parameters are documented there, so baseline is 3. The description confirms 'region' means a voice region for a call but adds no valid values or format hints beyond the schema.

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: 'Change the voice region of a DM/group call', plus the underlying endpoint. The DM/group scope implicitly separates it from guild voice-state tools, but no sibling is 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 DM/group-call scoping implies when the tool applies, but there is no explicit when-to-use, when-not, or named alternative (e.g. modify_current_user_voice_state for a user's own state). Guidance must be inferred from the resource wording.

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