Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

stop_ringing_channel_recipients

Stops ringing recipients in a Discord DM or group DM call, or declines an incoming call when your own user ID is provided.

Instructions

Stop ringing people in a DM/group DM call (or decline an incoming call by passing your own ID). [POST /channels/{channel_id}/call/stop-ringing]

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": "stop_ringing_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

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, non-destructive, open-world operation, so the safety profile is covered. The description adds the POST endpoint and the decline-via-self-ID behavior, but leaves unclear whether ringing stops for everyone or only the listed recipients, and whether the call is terminated. That effect-scope gap is the main missing behavioral detail.

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?

A single front-loaded sentence plus an endpoint annotation, with no filler. The bracketed POST path is mildly redundant but gives an API mapping that some agents find useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, the description covers purpose and one usage trick but omits the behavior of the optional recipients list and the outcome of the call. An agent can invoke it, but cannot fully predict the effect.

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 coverage is 50%: channel_id is documented while recipients is described only as 'recipients'. The description's 'passing your own ID' adds the one genuinely useful semantic hint about recipients, but does not explain the default when recipients is absent (presumably stop ringing everyone), leaving the ambiguous parameter under-specified.

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 uses a specific verb+resource ('Stop ringing people in a DM/group DM call') and scopes it to DM/group DM calls. It implicitly contrasts with the ringing sibling, but never names an alternative, so the distinction relies on the reader knowing the opposite operation exists.

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?

It gives a real usage scenario beyond the name: pass your own ID to decline an incoming call. It does not say when to prefer this over related siblings (e.g. leave_voice_channel) or what happens if recipients is omitted, so the guidance stops short of full when/when-not coverage.

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