Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_user_linked_connections

Read-only

Retrieve the third-party accounts and services linked to the authenticated Discord user by calling GET /users/@me/linked-connections, so assistants can inspect available connections.

Instructions

List User Linked Connections. [GET /users/@me/linked-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_linked_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's one real contribution beyond them is the /users/@me route, which reveals the operation is scoped to the current authenticated user rather than an arbitrary user ID. It says nothing about pagination, result shape, or whether linked connections include third-party account data.

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

Conciseness4/5

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

The description is a single short statement with the operation front-loaded and the route appended as supporting detail — no filler or redundancy. Its limitation is under-specification rather than verbosity, so brevity alone earns a solid but not top score.

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 zero-parameter read-only listing with annotations covering safety and no output schema, very little description is strictly required. Still, the definition omits what a 'linked connection' contains and how it differs from the sibling list_user_connections, leaving a real ambiguity an agent must resolve by guessing.

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 an empty object, so there is no parameter meaning for the description to add. Baseline for a parameterless tool applies, and no contradiction or confusion is introduced.

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 states a specific verb and resource (list user linked connections), so the basic operation is identifiable. However, it is essentially a restatement of the tool name plus an HTTP route, and it does nothing to distinguish 'linked connections' from the nearby list_user_connections, which an agent could easily confuse it with.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only implicit signal is the [GET /users/@me/linked-connections] path, which hints the tool targets the authenticated user, but the agent is left to infer that comparison against list_user_connections 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