Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_friend_nickname

Set a private nickname for a Discord friend by user ID. Use it to label contacts with a personal name visible only to you, or pass a null nickname to clear it.

Instructions

Set a private nickname for a friend. [PATCH /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": "set_friend_nickname"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
nicknameNo

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 this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds the useful detail that the nickname is private (visibility scoped to the caller), but says nothing about reversibility, required permissions, or what happens to the previous value.

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 sentences, front-loaded with the action, with the endpoint appended as compact technical context. No filler, though the bracketed path adds little an agent can act on beyond what the name already conveys.

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 two-parameter mutation with no output schema, the definition covers the core action but omits two things an agent would need: that a null nickname removes it, and that the target must be an existing friend. Adequate but incomplete at the edges.

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 is only 50% and the existing property descriptions are tautological ("User ID", "nickname"). The description does not explain the meaningful ambiguity the schema exposes: nickname accepts null via anyOf, which presumably clears the nickname, and that behavior is never stated.

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?

"Set a private nickname for a friend" gives a concrete verb (set), resource (nickname), and target scope (a friend), which separates it from set_my_nickname and set_member_nickname without naming them. The HTTP path annotation reinforces the resource, though it never explicitly contrasts against the server-member variant.

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: "for a friend" and "private" signal this applies to a personal relationship rather than guild members or the caller's own account. There is no explicit when-to-use statement, no mention of prerequisites (an existing friend relationship), and no named alternative for the neighbouring cases.

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