Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_current_user

Read-only

Retrieve your own Discord account details—username, email, phone, MFA status, and Nitro—to verify profile settings or account state.

Instructions

Get your own account (username, email, phone, MFA, Nitro…). [GET /users/@me]

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": "get_current_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
with_analytics_tokenNowith analytics token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the field list returned by the call, which is useful given no output schema, but says nothing about auth scope, rate limits, or what the unhelpful analytics-token flag actually changes.

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?

One short sentence plus an endpoint hint, front-loaded with the verb and resource. Nothing is padded, though the bracketed HTTP endpoint adds little for an MCP agent already given the tool name.

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 zero-required-parameter read tool with full annotation coverage, listing the returned fields is about the right amount of information. The only remaining gap is the semantics of the analytics-token flag, a minor omission.

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 description coverage is 100% for the single optional parameter with_analytics_token, so the baseline is 3. The description does not clarify what the flag does, meaning the agent gets no meaning beyond the schema's own terse text.

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 your own account') plus the fields returned (username, email, phone, MFA, Nitro). The qualifier 'your own' implicitly separates it from the sibling get_user, which fetches other accounts, though the alternate is never named.

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: it is the tool for the authenticated caller's own profile versus other users' profiles. There is no explicit when-to-use, no exclusion of the modify_current_user sibling (read vs write is left to inference), and no prerequisites stated.

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