Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_user_connections

Read-only

Retrieves the connections linked to the authenticated Discord account, such as external accounts and services, so you can review which integrations are attached to the user.

Instructions

List User Connections. [GET /users/@me/connections]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/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 nothing beyond the endpoint path: it does not explain that these are third-party linked accounts (e.g. Twitch/Steam), whether any auth scope is required, or what shape the response takes.

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 text is short and front-loaded with zero filler, which is good. However, the first sentence merely echoes the tool name and the second is a raw route, so neither sentence contributes much beyond structured data.

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?

This is a simple, zero-parameter read tool whose annotations carry the safety profile, so the bar is low. Even so, the description leaves the core semantics of "connection" undefined and gives no indication of response content, which is the one thing an agent cannot infer here.

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; baseline 4 applies. The endpoint path in brackets is a small extra hint about implicit targeting of the current user.

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

Purpose2/5

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

The description restates the tool name almost verbatim ("List User Connections") and adds only the raw HTTP route. The route does hint at the /users/@me scope, but nothing distinguishes this from siblings such as list_user_linked_connections or list_user_connection_subreddits, so an agent cannot tell which listing tool fits.

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, when-not-to-use, or alternative-routing guidance. The agent gets no signal about when this endpoint is preferable to the several other connection-related list tools.

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