Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guilds

Read-only

Retrieves the Discord servers you belong to, including names, IDs, member counts, owners, and live unread or mention counts.

Instructions

List the servers you are in (name, id, member counts, owner, unread/mention counts when live).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive and open-world behavior, so the safety profile is covered. The description still adds real context beyond them: it enumerates the returned fields (name, id, member counts, owner) and notes that unread/mention counts appear only "when live", which is a conditional-data caveat an agent cannot get from structured fields.

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?

A single sentence with the scope statement front-loaded and the field list tucked into a parenthetical. Every clause earns its place; the only minor cost is that the dense parenthetical slightly blurs the distinction between always-present and conditional fields.

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?

With no output schema and no parameters, the description carries the burden of telling the agent what comes back, and it does so by listing the key fields plus the conditional unread/mention data. It omits ordering, pagination or result-size limits, which leaves a small gap for a list operation that could return many servers.

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 no parameter meaning to explain and the baseline of 4 applies. The description does not fabricate parameter claims it cannot back.

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?

Names a specific verb ("List") and resource ("servers"), and scopes it to "the servers you are in", which implicitly separates it from discovery-oriented siblings like list_discoverable_guilds. It stops short of explicitly naming an alternative, so an agent must infer the boundary from the phrase "you are in".

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: "the servers you are in" signals this is the tool for enumerating joined servers rather than discoverable ones. There is no explicit when-to-use statement, no exclusion of the search_/discoverable siblings, and no mention of prerequisites such as authentication context.

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