Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_user_profile

Fetch a Discord user's profile details, including bio, pronouns, and mutual servers, by user ID to understand or verify account context.

Instructions

Fetch a user profile (bio, pronouns, mutual servers) as returned by Discord.

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": {
      "userId": "<userId>"
    },
    "name": "discord_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It hints that results are raw Discord shapes and names the returned fields, but says nothing about permission or OAuth scopes required for mutual servers, rate limits, or error behavior on an invalid or unknown snowflake.

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 well-formed sentence that front-loads the action and immediately lists returned data. Nothing is wasted, though the brevity contributes to the guidance gaps noted elsewhere.

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?

With no annotations and no output schema, the description does useful work by enumerating the main return fields. However, for a tool that plausibly overlaps with discord_get_user and discord_account_profile, it does not supply the differentiation or access requirements an agent needs to call it confidently.

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 100% and the single userId parameter is fully documented with a regex pattern and snowflake description, so the schema does the work. The description adds no further meaning about the identifier beyond what the schema already states.

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 states a specific verb and resource ("Fetch a user profile") and enumerates the payload (bio, pronouns, mutual servers), so the agent knows exactly what data comes back. It stops short of distinguishing this from siblings like discord_get_user or discord_account_profile, leaving genuine ambiguity about which profile tool to call.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. Given siblings such as discord_account_profile and discord_get_user that plausibly overlap, this silence is a real selection risk rather than a minor omission.

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