Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_guilds

List Discord servers the account is a member of, optionally filtered by server name and limited in count, so agents can identify guilds to work with.

Instructions

List servers the account is a member of.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoCase-insensitive substring of the server name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state pagination behavior, result ordering, permission requirements, or what happens when the limit is exceeded, leaving the agent with only the bare implication that this is a read operation.

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 single sentence is front-loaded and wastes no words, but its brevity reflects under-specification rather than efficiency. There is no structure beyond one clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter listing tool with no annotations and no output schema, the description is far too thin. An agent still needs to know how results are paginated or ordered, what the return shape is, and how the optional filters interact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: the 'query' parameter is documented in the schema, but 'limit' has no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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?

The description states a specific verb and resource: 'List servers the account is a member of,' which clearly describes a read operation over the account's guild membership. It lacks sibling differentiation, but the resource (guilds/servers) is distinct enough that an agent can tell it apart from discord_list_channels or discord_list_members without opening the schema.

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 guidance, no mention of alternatives for related lookups, and no indication of when this tool is inappropriate. The agent must infer all usage context from the tool name alone.

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