Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_relationship

Destructive

Remove a Discord friend, cancel or decline a friend request, or unblock a user by ID to manage account relationships.

Instructions

Remove a friend, cancel/decline a friend request, or unblock a user. [DELETE /users/@me/relationships/{user_id}]

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_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value by clarifying that the same call covers unblocking and request cancellation, not just unfriending. It says nothing about idempotency, behavior when no relationship exists, or whether the removed relationship can be restored.

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?

A single front-loaded sentence covers all three behaviors, followed by the endpoint for implementation context. No redundant or filler wording.

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 one-parameter tool with full schema coverage and annotations declaring destructiveness, the definition is essentially sufficient. The remaining gap is disambiguation from the similarly named remove_friend and bulk_remove_relationships siblings, which would matter to an agent choosing among them.

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?

With one required parameter at 100% schema coverage, the schema already carries the documentation burden. The endpoint template [DELETE /users/@me/relationships/{user_id}] implicitly confirms that user_id identifies the other party in the relationship rather than the caller, which is a small addition beyond the bare 'User ID' schema text.

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 (remove) and enumerates the three distinct relationship states it can affect: friend removal, friend-request cancel/decline, and unblock. It does not differentiate itself from the overlapping sibling remove_friend or from bulk_remove_relationships, so an agent cannot resolve the naming overlap from this text alone.

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?

Use contexts are stated clearly via the three enumerated scenarios, which tell an agent exactly which relationship states the tool handles. There are no explicit exclusions or named alternatives, and nothing says what to do when the target has no relationship with the caller.

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