Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_user_note

Set a private note on a Discord user that only you can see, letting you record context or reminders tied to that account.

Instructions

Set your private note on a user (only you can see it). [PUT /users/@me/notes/{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>",
      "note": "<note>"
    },
    "name": "set_user_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
user_idYesUser ID

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 readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write/non-destructive profile is covered. The description adds real value by disclosing that the note is private to the calling user, but it omits what happens when note is null (clear vs. ignore) and does not mention the return payload or any overwrite semantics.

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 compact clauses with the privacy constraint front-loaded and the endpoint appended as an aside. Nothing is wasted, though the bracketed HTTP route adds little for an agent that already has the tool name.

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 privacy aspect but leaves the null-note behavior and the response/return shape unexplained. Adequate to invoke, but not complete on the edge case the schema explicitly permits.

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%, with both parameters carrying short descriptions ('User ID', 'Note text'), so the structured data does most of the work. The description adds no meaning about the nullable note parameter — a notable gap given the anyOf string/null type suggests clearing behavior that is never explained.

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?

States a specific verb and resource: setting a private note on a user, plus the privacy qualifier '(only you can see it)' and the underlying PUT endpoint. That distinguishes it from a read-oriented sibling like get_user_note, though it never names the sibling explicitly.

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?

The description implies usage by describing the action but gives no explicit when-to-use, when-not-to-use, or prerequisite guidance. It does not tell the agent how this relates to get_user_note or get_user_notes, so the agent must infer that this is the write counterpart.

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