Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

find_users

Read-only

Search for people by name across friends, DM contacts, and server members when a guild ID is provided.

Instructions

Find people by name among your friends, DM contacts and (with guild_id) a server's members.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
guild_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by bounding the search domain to the caller's social graph rather than all users, but says nothing about result size, ranking, or whether partial matches are returned.

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 sentence, front-loaded with the action and resource, with the conditional guild_id caveat correctly placed as a parenthetical rather than a trailing afterthought. Nothing superfluous, though the friend/DM-contact enumeration could be marginally tighter.

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?

For a simple three-parameter read-only lookup with no output schema, the description covers what the tool searches and over which scope. It leaves gaps on result shape, result limits, and the undocumented 'limit' parameter that an agent would need to call it precisely.

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

Parameters4/5

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

With 0% schema description coverage, the description must supply meaning: it clarifies that 'query' is a name match and that 'guild_id' scopes the search to a server's members. The third parameter, 'limit', is left entirely undocumented in both schema and description.

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 a specific verb (find) and resource (people/users) plus the exact search scope: friends, DM contacts, and optionally a server's members. That scope statement separates it from find_channels without needing to name it, though no sibling is explicitly referenced.

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 parenthetical '(with guild_id)' implies that server-member search requires that parameter, giving conditional guidance. However, there is no statement of when not to use it, no named alternative for channel or message lookups, and no note on what happens when the query matches nothing.

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