Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

accept_friend_request

Accept an incoming Discord friend request, or send one using a user ID, to connect your account with another user.

Instructions

Accept an incoming friend request (or send one by 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": "accept_friend_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already indicate this is a non-read-only, non-destructive, open-world operation, but the description adds little behavioral context. It does not explain what accepting changes, whether it creates a mutual friendship, what happens on failure, or how it differs from sending a request.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but the parenthetical adds ambiguity rather than useful detail. It is concise at the cost of clarity.

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?

For a simple one-parameter mutation tool, the description still omits essential context: the meaning of user_id in the accept flow and how this differs from send_friend_request. It is not complete enough to guide reliable invocation.

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?

Schema coverage for the single user_id parameter is 0%, so the description must carry the burden. It only vaguely says 'by user ID' and does not reconcile that with the 'incoming friend request' acceptance flow, leaving the parameter's exact meaning ambiguous.

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

Purpose2/5

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

The first clause clearly says it accepts an incoming friend request, but the parenthetical '(or send one by user ID)' introduces a different operation and conflicts with the sibling send_friend_request. An agent cannot confidently tell whether this tool only accepts requests or also sends them.

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 guidance on when to use this tool versus send_friend_request or other friend-related siblings. It also does not clarify whether user_id refers to the requester, the recipient, or a request identifier.

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