Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_discoverable_guilds

Read-only

Browse and filter featured public Discord servers by guild, category, or application, using pagination to find discoverable communities.

Instructions

Browse featured public servers. [GET /discoverable-guilds]

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoSkip this many results
guild_idsNoguild ids
categoriesNocategories
application_idsNoapplication ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 externally. The description contributes only the HTTP path, and says nothing about auth requirements, default/max page size, or what "featured" means in the returned set.

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?

Two short, front-loaded sentences with no padding, and the resource is stated before the endpoint detail. The endpoint tag is mildly redundant with the tool name but not wasteful.

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?

With five filter/pagination parameters and no output schema, an agent needs to know roughly what comes back and how paging behaves; neither is covered. The definition is too thin for a discovery-listing tool that has a closely named search sibling.

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

Parameters3/5

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

Schema description coverage is 100% across all five optional parameters (limit, offset, guild_ids, categories, application_ids), so the schema carries the parameter burden. The description adds no meaning about how filters combine or interact with pagination, leaving this at the baseline.

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 gives a concrete verb+resource ("Browse featured public servers") and the bracketed endpoint confirms it maps to the discovery listing. It does not differentiate this from the sibling search_discoverable_guilds or clarify that "servers" means guilds, so it falls short of the 5 bar.

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 guidance on when to use this rather than search_discoverable_guilds, which is the obvious alternative for filtered/query-based discovery. No preconditions, no mention of paging through results, no exclusions.

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