Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_relationships

Read-only

Lists all Discord relationships in raw form, including friends, blocked users, incoming requests, and outgoing requests, so you can inspect connection status by type.

Instructions

List all relationships raw (type 1 friend, 2 blocked, 3 incoming request, 4 outgoing request). For a readable list use list_friends. [GET /users/@me/relationships]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/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 genuinely useful behavioral context beyond that: the underlying endpoint (GET /users/@me/relationships) and the meaning of the 'raw' numeric type codes, which tells the agent what the returned records look like even without an output schema.

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?

Two compact clauses with the purpose and type-code key front-loaded, followed by the alternative-tool redirect and the endpoint. Zero filler.

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-parameter read-only list tool with no output schema, the description covers what it does, the shape of the raw values, and the alternative. It does not mention pagination or result limits, but nothing else an agent needs to call it correctly is missing.

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 no parameters, so per the baseline this is a 4. The description adds nothing about parameters because there is nothing to add.

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

Purpose5/5

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

States a specific verb and resource ('List all relationships raw'), decodes the numeric type field inline (1 friend, 2 blocked, 3 incoming request, 4 outgoing request), and names the sibling it is not ('For a readable list use list_friends'). An agent can distinguish it from list_friends without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to list_friends when a readable/human-friendly list is wanted, which is the main selection decision here. It does not discuss when raw output would be preferred (e.g., machine filtering on type codes), but the practical guidance is clear.

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