Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_friend

Destructive

Removes a Discord friend or cancels/declines a pending friend request by user ID.

Instructions

Remove a friend (or cancel/decline a friend request).

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": {
      "user_id": "<user_id>"
    },
    "name": "remove_friend"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/destructive nature is covered. The description adds real scope information beyond the annotations — that it also cancels or declines pending requests, not just existing friendships. It stops short of stating whether the removal is bidirectional, irreversible, or what permissions are needed.

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 short sentence with zero filler, and the core action is front-loaded. The parenthetical is an efficient way to fold in the second use case without a separate sentence.

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 destructive one-param tool with no output schema, the description covers what the tool does and its two scenarios but omits the parameter's expected format and any account of side effects or failure cases. Annotations handle the safety profile, so the remaining gap is moderate rather than severe.

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?

There is a single required parameter, user_id, with 0% schema description coverage, yet the description never mentions it or clarifies whether it accepts a user ID, tag, or username. For one param with no schema documentation, the description should carry the burden and does not.

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+resource ("Remove a friend") and extends scope to "cancel/decline a friend request", which distinguishes it from accept_friend_request and add_friend. It does not address how it differs from remove_relationship or bulk_remove_relationships, leaving some sibling ambiguity.

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 parenthetical implies two use cases: ending an existing friendship and rejecting a pending request. It gives no explicit when-not guidance and names no alternative tool, so the agent must infer the boundary with remove_relationship.

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