discord-admin-mcp

Overview Schema Source Related Servers Discussions Admin

search_members

Search Discord server members whose username or nickname begins with a query, scoped to a guild and capped by a result limit.

Instructions

Busca membros cujo nome ou apelido comeÃ§a com query.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`guild_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the matching rule (prefix, against name or nickname), but says nothing about read-only safety, whether bots are returned, how limit/pagination behaves, or permission requirements.

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?

A single front-loaded sentence with no filler; the pattern-match semantics come first. It is efficiently written, though the brevity contributes to the coverage gaps noted elsewhere rather than being a virtue on its own.

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?

An output schema exists, so return-value explanation is not required. However, for a 3-parameter search tool with zero annotation and zero schema coverage, the definition leaves required inputs like guild_id and limit behavior unexplained, which is a meaningful gap.

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 description coverage is 0%, so the description must compensate and does not. It indirectly defines query semantics ('começa com'), which is real added meaning, but guild_id and limit (including the default of 25) are left completely undocumented in both schema and prose.

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?

The description names a specific verb ('Busca') and resource ('membros') plus the matching scope: prefix match on name or nickname. That is more precise than the bare tool name, but it never distinguishes this from sibling list_members, so an agent cannot tell which of the two to pick from the text alone.

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 guidance on when to use this versus list_members, no exclusion, and no note that a guild_id is required to scope the search. The agent must infer the usage context entirely from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.