Find Discord server members by username or nickname prefix. Specify a query and optionally a server ID and limit to get matching results.
Search for members in a server by username or nickname prefix
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-100, default: 20) | |
| query | Yes | Query string to match names against | |
| guildId | No | Discord server ID (defaults to DISCORD_GUILD_ID) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It says nothing about result ordering, case sensitivity, whether nickname and username are both matched or OR'd, pagination behavior, or what happens when no prefix matches (empty result vs error).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with a clear verb-resource-scope structure and no wasted words. Nothing is buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, no annotations, and no behavior described beyond the matching rule. For a search tool among ~90 siblings, the agent needs to know ordering, case handling, and how it differs from list_members, none of which is present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so each parameter already has its own description; the description adds nothing beyond what the schema says. Baseline 3 is appropriate when the schema does all parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (search) and resource (members) and constrains matching to username or nickname prefix. It does not reference the close sibling list_members, so the agent cannot tell from the description alone why search is preferred in a given situation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage (need prefix search rather than full listing), but no explicit when-to-use rule and no mention of list_members as the alternative. The agent must infer the choice from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.