Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_get_user_info

Fetch profile details for yourself or another Discord user by ID, defaulting to your own account when no ID is provided.

Instructions

Fetch profile details for yourself or another user by ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_get_user_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNoTarget Discord User ID (defaults to yourself).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and 'Fetch' only weakly implies a read-only operation. It does not disclose permission requirements, what happens with invalid or inaccessible user IDs, what fields are returned, or any rate-limit considerations.

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 front-loaded sentence with no waste or hedging. It is arguably too terse for a tool with no annotations, but there is no structural or redundancy problem.

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 simple one-parameter read tool this is adequate, but with no output schema the description never indicates what 'profile details' includes, and with no annotations it omits any behavioral framing. Just enough to call it, not enough to predict the result.

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 schema already documents the user_id parameter with its self-defaulting behavior. The description's 'by ID' and 'yourself' phrasing adds nothing the schema does not already say, so baseline 3 applies.

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 ('Fetch profile details') plus the scope ('yourself or another user by ID'), which is unambiguous for an agent. It does not distinguish itself from related siblings like discord_list_guild_members or discord_list_friends, so it stops 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?

Calling with no argument to get your own profile is implied by 'yourself or another user,' which gives some usage context. However, there is no explicit guidance on when to prefer this over member/friend listings or when profile fetches are appropriate versus other user-related tools.

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