Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

send_custom_call_sound

Sends a custom call sound to a Discord channel by providing the channel ID plus animation type and ID, enabling custom call audio playback.

Instructions

Send Custom Call Sound. [POST /channels/{channel_id}/custom-call-sounds]

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>",
      "animation_type": "<animation_type>",
      "animation_id": "<animation_id>"
    },
    "name": "send_custom_call_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
animation_idYesanimation id
animation_typeYesanimation type

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 mutation profile is covered. The description adds only the endpoint path, which largely restates the write semantics; it says nothing about permission requirements (e.g. needing to be connected to the call), whether the referenced sound must already exist, or what happens on failure.

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?

The text is short and front-loaded, with the endpoint bracketed as secondary detail, so nothing is padded. But its brevity reflects under-specification rather than efficient information density — there is only one substantive phrase.

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 three-required-parameter mutation tool with no output schema, and the annotations cover only the safety profile. The description omits prerequisites (membership in the call, valid sound reference), expected effects in the channel, and error behavior, leaving too much for the agent to infer before calling.

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%, so the baseline of 3 applies. The description adds no meaning beyond the schema, and notably leaves unaddressed why a sound tool takes animation_type and animation_id parameters, which the schema labels only as "animation type" and "animation id".

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 gives a verb+resource ("Send Custom Call Sound") and the backing endpoint POST /channels/{channel_id}/custom-call-sounds, so the channel-scoped write nature is inferable. However, it never explains what a "custom call sound" is or how it differs from sibling actions such as send_soundboard_sound or send_voice_channel_effect, so an agent must guess at the distinction.

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 or when-not-to-use guidance at all, despite several plausible sibling alternatives (send_soundboard_sound, send_voice_channel_effect) that could be confused with this one. The only contextual cue is the HTTP path, from which channel scoping can be inferred but not the selection criteria.

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