Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_discoverable_guilds

Read-only

Search public servers in Discord's Server Discovery by text query, with category filters and pagination, to find communities matching your interests.

Instructions

Search public servers in Server Discovery. [GET /discoverable-guilds/search]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_discoverable_guilds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesSearch text
offsetNoSkip this many results
categoriesNocategories

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, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the REST endpoint string; it says nothing about result ordering, pagination limits, rate limiting, or what a search over public servers actually returns beyond the annotations' open-world hint.

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?

One sentence plus a bracketed route tag, with the resource scope front-loaded and zero filler. Nothing is wasted, though the extreme brevity leaves gaps the tool's complexity would justify filling.

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?

Four parameters, one required, no output schema, and full schema coverage mean the structured data does most of the work. Still, a discovery search tool would benefit from a note on pagination behavior and the meaning of category IDs, which neither the description nor schema clarifies beyond 'categories'.

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%, so all four parameters (query, limit, offset, categories) are already documented in the schema. The description adds no meaning beyond that, which meets the baseline-3 expectation when the schema carries the load.

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?

States a specific verb ('Search') and resource ('public servers in Server Discovery'), plus the underlying route GET /discoverable-guilds/search. The search-vs-list contrast with siblings like list_discoverable_guilds is inferable from the verb but never made explicit.

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?

No when-to-use or when-not-to-use guidance. It never says how this differs from list_discoverable_guilds, search_published_guilds, or search_directory_entries, all of which appear to operate in adjacent territory. The agent must guess from names 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