Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

ring_channel_recipients

Rings selected recipients in an active Discord DM or group DM call; leave recipients empty to ring everyone.

Instructions

Ring people in a DM/group DM call (start a call with join_voice_channel first). Empty recipients rings everyone. [POST /channels/{channel_id}/call/ring]

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world POST, so the bar is lower. The description still adds real behavior beyond annotations: the call must already exist, and an empty recipients list broadcasts to everyone — a meaningful side-effect distinction. It does not cover permission requirements or what happens if no call is active.

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?

Three compact clauses, front-loaded with the action, then the prerequisite, then the edge-case semantics, with the endpoint as a trailing identifier. Nothing is padded or redundant.

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 mutation with no output schema and existing annotations, this covers action, ordering prerequisite, and the null-recipients default — enough to call it correctly. It leaves out error conditions (no active call, missing permissions) and any indication of what the response contains.

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

Parameters4/5

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

Schema coverage is 50% and the `recipients` schema description is merely 'recipients', so the description carries the load by explaining that an empty list rings everyone. `channel_id` meaning is already well documented in the schema, so the added value is concentrated in the one ambiguous parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Ring people in a DM/group DM call') plus the underlying endpoint, which tells an agent exactly what action occurs. It is clearly separable from siblings like stop_ringing_channel_recipients and join_voice_channel without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete prerequisite ('start a call with join_voice_channel first'), which prevents a common ordering mistake, and clarifies the empty-list case. It stops short of naming when-not-to-use or the stop-ringing alternative explicitly, so it falls short of full routing guidance.

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