Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_account_profile

Fetch public profile fields of the logged-in Discord account to identify the active user and inspect available account details.

Instructions

Public profile fields of the logged-in account.

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_account_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. 'Public profile fields' usefully hints that only publicly visible data is returned rather than private details like email, but it says nothing about auth requirements, failure modes, or what the response looks like. For a zero-annotation tool this leaves most behavioral questions unanswered.

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

Conciseness3/5

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

The single short fragment wastes no words, but it is a sentence fragment rather than a structured, front-loaded description, and its brevity comes at the cost of under-specification rather than genuine economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place an agent can learn what 'public profile fields' actually contains, and it never enumerates them. For a trivial read tool the bar is low, but the return values are exactly the information an agent needs here and they are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('public profile fields') and scopes it to 'the logged-in account', which does separate it from the ID-based siblings like discord_get_user. However, it is a bare noun phrase with no verb, and it never names or contrasts with discord_user_profile or discord_guild_member_me, so the agent must still infer 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 at all: no statement of the condition that selects this over discord_user_profile, discord_get_user, or discord_guild_member_me, and no prerequisites or exclusions. The only implicit cue is 'logged-in account', which the agent must interpret on its own.

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