Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_friends

Read-only

Lists your Discord friends, blocked users, and incoming or outgoing friend requests in readable form, with an option to filter by relationship type.

Instructions

List friends, blocked users and pending friend requests in readable form.

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

Input Schema

NameRequiredDescriptionDefault
typeNoDefault all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 only "in readable form," which usefully signals human-readable rendering rather than raw IDs, but says nothing about pagination, ordering, or how blocked/request lists interleave when type=all.

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?

One sentence, front-loaded with the verb and the enumerated resources, with no filler or redundancy. Nothing could be removed without losing information.

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 read-only, single-optional-param list tool with annotations and no output schema, the description covers scope adequately. The only real gap is whether type=all merges the four categories into one list or returns them separately, which matters for interpreting output.

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% with a single enum parameter already documented as "Default all," so the schema carries the parameter semantics. The description lists the categories the enum covers but adds no format or behavioral nuance (e.g., what 'all' returns together).

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?

Specific verb ("List") plus explicit resources (friends, blocked users, pending friend requests), which maps cleanly onto the enum values friend/blocked/incoming_request/outgoing_request. It distinguishes itself from siblings like list_friend_suggestions, though it never names an alternative explicitly.

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: an agent can infer this is the read path for relationship data, and the schema's "Default all" hints at the default behavior. There is no statement of when to prefer this over list_friend_suggestions or list_dms, and no prerequisites such as needing an authenticated user.

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