Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_friends

Retrieves the account's Discord friends and includes nicknames where configured, so agents can identify available contacts.

Instructions

List friends of the account, with nicknames when set.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden; it does add one real behavioral detail beyond the empty schema — that nicknames are included when set — which hints at the return shape. However, it says nothing about whose account is queried, whether results are paginated or capped, or whether this is strictly a read operation, all of which an unannotated tool should address.

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?

A single short sentence with the core action front-loaded and one useful qualifier appended. Nothing is redundant or padded, and the size matches the simplicity of a zero-argument list tool.

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 no-parameter read tool with no output schema, the definition covers the essentials but leaves the return contract thin — no indication of result size, ordering, or pagination, and "the account" is ambiguous between the authenticated user and the bot. Adequate to invoke, but not complete enough to predict the response.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter text is needed or missing.

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 ("List friends of the account") and adds a scope note about nicknames. It is clearly distinct from most siblings by name, but it never explicitly contrasts with close neighbors like discord_list_friend_requests or discord_list_blocked, leaving that differentiation to the reader.

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 or when-not-to-use guidance, and no mention of prerequisites or alternatives. The agent must infer from the name alone that this returns the account's accepted friends rather than pending requests or blocked users.

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