Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_published_guilds

Read-only

Find published Discord guilds by text query and paginate discovery results using limit and offset.

Instructions

Search Published Guilds. [GET /discovery/search]

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryNoSearch text
offsetNoSkip this many results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/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 safety and open-world reach are covered. The description adds only the REST endpoint, with no detail on result ordering, filtering semantics, rate limits, or what 'published' excludes, which is the one thing structured data cannot convey.

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?

It is extremely short and front-loaded, but the second sentence (the endpoint tag) adds almost no decision value for an agent. Brevity here results from under-specification more than curation.

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 search tool with pagination parameters, no output schema, and no explanation of what a result contains or how paging terminates, the description leaves real gaps. The annotations cover safety only, not search behavior.

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% (limit, query, offset all documented inline), so the schema carries the parameter burden and baseline 3 applies. The description contributes nothing beyond that, but nothing is lost either.

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

Purpose2/5

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

"Search Published Guilds" restates the tool name almost verbatim and adds only an HTTP route tag. It never distinguishes this from siblings like search_discoverable_guilds or list_discoverable_guilds, so an agent cannot tell which search surface applies.

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 prerequisite or scope conditions, and no alternative named. The agent must infer from the name alone when published-guild search is the right call.

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