Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

query_guild_members

Read-only

Search a Discord server's members by username or nickname prefix to find matching guild users; intended for bot accounts.

Instructions

Search server members whose username/nickname starts with a query (REST; bots). User accounts: use search_members. [GET /guilds/{guild_id}/members/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": {
      "guild_id": "<guild_id>"
    },
    "name": "query_guild_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryNoSearch text
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 the safety profile is covered. The description adds the important qualifier that search matches only the start of the username/nickname and requires bot auth, but says nothing about pagination, result caps, or return shape.

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?

It is two compact fragments plus a bracketed endpoint, with the matching rule and the auth constraint front-loaded. No sentence is wasted.

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

Completeness4/5

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

For a simple three-parameter read tool with full schema coverage and no output schema, the definition supplies what an agent needs to pick it correctly and scope the query. It lacks only return-format and pagination detail, which is a minor gap given the annotations.

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 coverage is 100% and all three parameters are documented, so the schema carries parameter meaning. The description only clarifies that 'query' is a prefix match against username/nickname, adding some value but no format or limit semantics beyond what the schema states.

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?

The description states a specific verb and resource (search server members), the matching rule (username/nickname prefix), and its REST endpoint. It also names the sibling to use for user accounts (search_members), so the agent can distinguish it without opening a 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?

It gives an explicit routing rule: bots should use this tool, user accounts should use search_members. It does not cover when to prefer list_guild_members or search_guild_members over this one, so it stops short of full when/when-not coverage.

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