Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_members

Read-only

Look up Discord server members by username/nickname prefix or user IDs through a live connection to identify members for moderation, mentions, or server administration.

Instructions

Look up server members by name prefix (or by user_ids) through the live connection — works for normal user accounts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax 100
queryNoUsername/nickname prefix ("" lists all, needs moderator permissions)
guild_idYes
user_idsNo
presencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that queries go 'through the live connection' (live gateway vs. cache/REST), but says nothing about rate limits, result ordering, or pagination for a 100-result cap.

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 front-loaded sentence with the primary use case first and the alternative mode second. No filler, though the em-dash caveat about normal user accounts could be folded more cleanly.

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 5 parameters, 40% schema coverage, and no output schema, the description leaves too much to inference — two parameters are entirely unexplained and the return shape (member objects? presence data?) is never characterized.

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

Parameters2/5

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

Schema coverage is only 40%, so the description must compensate and only partially does: it explains query (name prefix) and user_ids usage but never mentions limit or presences, both of which lack schema descriptions. An agent gets no guidance on what presences does or how limit interacts with the 'Max 100' hint.

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 specific verb and resource ('look up server members') plus two retrieval modes (name prefix, user_ids). However, siblings like search_guild_members, query_guild_members, and list_guild_members are not distinguished, so the agent cannot tell from the description alone which one to pick.

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

Usage Guidelines3/5

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

The clause 'works for normal user accounts' implicitly positions this tool for user-account sessions rather than bot accounts, which is a useful selection signal, but there is no explicit when-to-use/when-not-to-use language and no named alternative.

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