Skip to main content
Glama

disdex: Discord server search

by io.disdex
OverviewDiscussionsAdmin

Search Discord servers

search_servers
Read-onlyIdempotent

Search public Discord servers indexed by disdex. Matches words against the server name, vanity URL, description, profile traits and guild tag. With a query, results are ranked by relevance (servers named for the query first, then matches in traits and descriptions, with bigger and more active servers first among similar matches); without one, by member count. Each result has its member and online counts, language, and a joinable invite link when one is known. If no server matches every word of a longer query, results match all but one word and partial_match is true. NSFW servers are never returned.

Input Schema

NameRequiredDescriptionDefault
tagNoOnly servers with this Discord guild tag (the short tag members can show next to their name), case-insensitive exact match.
sortNoDefaults to relevance with a query and members without one. members/online/boosts sort largest first; newest/oldest sort by when the server was created on Discord.
limitNo
queryNoSearch words, at least 3 letters or digits (e.g. "minecraft survival", "study group"). Omit to browse everything by the chosen sort.
offsetNo
languageNoOnly servers whose name and description are in this language: an ISO 639-1 code such as en, es, de, pt, ru, ja.
growing_within_daysNoOnly servers whose member count was seen going up within this many days. A quick filter for active, growing communities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / sort / default
      Removed value: -"members"
    • changedInput schema / properties / sort / description
      Previous value: -"members/online/boosts sort largest first; newest/oldest sort by when the server was created on Discord."New value: +"Defaults to relevance with a query and members without one. members/online/boosts sort largest first; newest/oldest sort by when the server was created on Discord."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "members",
-  "online",
-  "boosts",
-  "newest",
-  "oldest"
-]New value: +[
+  "relevance",
+  "members",
+  "online",
+  "boosts",
+  "newest",
+  "oldest"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description's job is to add context beyond that, and it does: relevance ranking order, the partial_match fallback for longer queries, and a hard guarantee that NSFW servers are never returned. It even lists the fields of each result including the conditional joinable invite link.

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

Conciseness5/5

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

Six sentences, each earning its place: purpose, matching fields, ranking rules, return contents, partial-match fallback, NSFW exclusion. The most important scoping facts (what is searched, how results are ordered, what is filtered out) are front-loaded.

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

Completeness5/5

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

With no output schema, the description takes on the burden and covers result contents (member/online counts, language, invite link). Combined with the fallback and NSFW behavior, an agent has everything needed to call and interpret this tool.

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?

Schema coverage is 71%, and the description supplements it by explaining the sort default ('relevance with a query and members without one') and the concept of browsing without a query. The tag, language, and growing_within_days parameters carry their own schema descriptions, so this is solid without being exhaustive.

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

Purpose5/5

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

States a specific verb and resource ('Search public Discord servers indexed by disdex') and enumerates exactly which fields are matched (name, vanity URL, description, traits, guild tag). This is detailed enough that an agent can distinguish it from lookup siblings like get_server without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage conditions: provide a query for relevance-ranked matching, omit it to 'browse everything by the chosen sort', and the schema-side descriptions cover the filters. It does not explicitly contrast with the sibling tools, so an agent must infer that check_invite/get_server are lookups rather than discovery.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All disdex: Discord server search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources