Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user_note

Read-only

Retrieves your private note for a specified Discord user by ID, so you can view saved reminders or context about that user.

Instructions

Your private note on a user. [GET /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>"
    },
    "name": "get_user_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuine behavioral detail beyond that — the note is private to the calling account, and the underlying GET endpoint is disclosed — but it says nothing about what happens when no note exists or what the response contains.

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

Conciseness5/5

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

Two compact fragments with the resource and scope front-loaded and nothing wasted. The endpoint reference is terse and adds orientation without bloating the definition.

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 one-parameter read tool with full schema coverage, no output schema, and annotations covering safety, the definition is nearly sufficient. The only real gap is the empty-result behavior, which an agent would want to know before calling.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines user_id. The phrase 'on a user' adds no syntax, format, or sourcing detail beyond what the schema provides, making the baseline 3 correct.

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 names a specific resource (a private note) scoped to a single user, and the bracketed endpoint confirms it is a retrieval of one note rather than a list. That implicitly separates it from get_user_notes and set_user_note, though no sibling is named explicitly.

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: an agent can infer this is the single-note read counterpart to the sibling list and write tools. There is no explicit when-to-use statement, no exclusion pointing to get_user_notes for listing, and no mention of prerequisites.

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