Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_friend_suggestion

Destructive

Dismisses a pending friend suggestion for a specified user ID via the Discord API, letting you clear suggestions you no longer want to see or act on.

Instructions

Remove Friend Suggestion. [DELETE /friend-suggestions/{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_friend_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 by structured data. The description adds only the HTTP verb and path, which is redundant with the name, and says nothing about irreversibility, idempotency, or what happens if no suggestion exists.

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?

Two short fragments with no filler, and the action is front-loaded. It is close to minimal, though the bracketed endpoint notation is arguably the only non-redundant element.

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 destructive, open-world mutation with no output schema and no explanation of consequences, required permissions, or failure behavior. For a simple one-parameter tool the schema covers the input, but the description leaves the agent without enough context to use it safely.

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 100% with a single required parameter, so the baseline applies. The only marginal addition is the "{user_id}" path segment in the URL, which confirms the ID identifies the target user rather than the caller, but no format or sourcing detail is given.

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 pairs a verb and resource ("Remove Friend Suggestion") with the HTTP route DELETE /friend-suggestions/{user_id}, so the basic action is identifiable. However, it largely paraphrases the tool name and does nothing to distinguish it from nearby siblings such as remove_friend or remove_relationship, which act on different objects.

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 statement of when to call this versus remove_friend, accept_friend_request, or list_friend_suggestions, and no prerequisites such as whether the suggestion must exist or whose suggestion can be removed. The agent must infer the usage context entirely from the name and endpoint.

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