Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

send_friend_request

Send a Discord friend request by username, with an optional note; handles new usernames that use discriminator 0 or omit it.

Instructions

Send a friend request by username (new usernames: discriminator "0" or omit). [POST /users/@me/relationships]

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": {
      "username": "<username>"
    },
    "name": "send_friend_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
usernameYesUsername

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that new usernames use discriminator "0" or omit it — plus the underlying POST endpoint, but says nothing about failure modes (already-friends, blocked, requests closed) or whether the request must be accepted to take effect.

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 a bracketed endpoint tag — nothing wasted. The endpoint tag is mildly redundant with the mutation semantics but is a useful factual anchor rather than filler.

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 two-parameter mutation with annotations covering mutability and no output schema, the description supplies the action, the target key, and the username-format edge case. The remaining gap is the absence of any statement about what a successful send produces or how the request fails.

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%: username is described only as "Username" and note only as "Note text". The description meaningfully upgrades the username parameter with discriminator handling that the schema lacks, but the optional note parameter is never mentioned, so compensation for the coverage gap is partial.

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 opens with a specific verb+resource ("Send a friend request") and adds the key selector ("by username"), which distinguishes it from accept_friend_request by implication of the direction of the action. It stops short of naming a sibling it must not be confused with, notably add_friend, which an agent might otherwise consider interchangeable.

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?

Usage is only implied: the agent learns it needs a username to target a person, and gets a formatting rule for new vs. legacy usernames. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as not already being friends or the target having requests disabled, and no routing away from similarly named siblings like add_friend.

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