Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user

Read-only

Retrieve a Discord user's basic public information by ID, enabling assistants to identify accounts and resolve profile details before responding or moderating.

Instructions

Get a user's basic public info. [GET /users/{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"
  }
}

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 only that the returned data is limited to public fields and cites the REST endpoint, without saying what happens for missing/invalid IDs or whether private fields are stripped.

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 sentences with the core purpose front-loaded and the endpoint mapping appended as secondary detail. Nothing is padded or repeated.

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 with no output schema and full annotation coverage, the description covers purpose, scope, and endpoint. The main residual gap is not enumerating the "basic public info" fields returned, though the annotations and schema carry most of the load.

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?

Single parameter with 100% schema description coverage, so the schema already carries the semantics. The description adds no format, type, or sourcing hints for user_id beyond what the schema states, making the baseline 3 appropriate.

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 ("Get a user's") and narrows scope with "basic public info," which distinguishes it from profile/settings siblings. It does not name any sibling explicitly, so it falls short of a 5.

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?

The phrase "basic public info" implies when to use this over a fuller lookup like get_user_profile, but there is no explicit when-to-use or when-not-to-use guidance and no mention of get_current_user as the alternative for the authenticated caller.

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