Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

send_voice_channel_effect

Send an emoji effect in your current voice channel to trigger a visual reaction during a call.

Instructions

Send an emoji effect in the voice channel you are in. [POST /channels/{channel_id}/voice-channel-effects]

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

Input Schema

NameRequiredDescriptionDefault
emoji_idNo
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
emoji_nameNo
animation_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 bar is lower. The description adds the POST endpoint and the in-voice prerequisite, which is genuine extra context. It does not mention rate limiting (a real concern for emoji effects), permission requirements, or what happens if the user is not in a voice channel.

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 imperative sentence plus the endpoint in brackets, front-loaded with the action. Nothing is redundant, though the endpoint annotation contributes little to an agent choosing or invoking the tool.

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?

This is a mutating, open-world POST with no output schema and 25% parameter coverage. The description omits how to select the emoji, what animation_type means operationally, and any error or rate-limit behavior — too much is left for the agent to infer for a 4-parameter write call.

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 description coverage is only 25%, so the description must compensate and it does not: emoji_id, emoji_name and animation_type are never mentioned. Critically, the description never says that an emoji must be identified via emoji_id or emoji_name, nor that animation_type takes 0/1 for premium/basic — all of which the schema states tersely at best.

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 specific verb and resource: sending an emoji effect into a voice channel, with the endpoint path supplied. It is clearly differentiable from siblings like send_soundboard_sound or send_custom_call_sound by the word 'emoji'. However, 'the voice channel you are in' sits awkwardly against the required channel_id parameter, leaving slight ambiguity about whether the channel is implicit or explicit.

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 phrase 'the voice channel you are in' implies a prerequisite (the caller must already be connected to voice), which is useful context. But there is no explicit statement of when to prefer this over send_custom_call_sound or send_soundboard_sound, and no exclusions or failure conditions are given.

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