Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

find_channels

Read-only

Locate Discord channels by name across all servers, or find direct-message channels by person name; requires an active live connection.

Instructions

Find channels by name across all your servers (and DMs by person name). Needs the live connection.

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_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
guild_idNo

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=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuine operational prerequisite ('Needs the live connection'), which is useful context. However, it says nothing about how many results come back, how limit affects behavior, or whether the search is fuzzy or exact.

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?

Two short sentences, front-loaded with the search semantics and ending with the connectivity prerequisite. No filler, though the parenthetical DM clause could be integrated 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?

For a three-parameter search tool with no output schema and zero schema documentation, the description is thin: result shape, result count, and the role of limit and guild_id are all unstated. The unexplained guild_id versus 'across all servers' tension is a real completeness 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 all three parameters (query, limit, guild_id) rest on the description, and it only clarifies that query is a person/channel name. It never explains what limit does or what guild_id scopes — indeed guild_id appears to conflict with the stated 'across all your servers' behavior, leaving that ambiguity unresolved.

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 and resource ('Find channels by name') plus the scope ('across all your servers') and even covers the DM exception ('DMs by person name'). This differentiates it reasonably from list-oriented siblings like list_guild_channels, though no sibling is named explicitly.

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?

Usage is only implied: the agent learns this is a by-name search across servers and that a live connection is required, which is a real prerequisite. There is no explicit when-to-use versus when-not guidance, and no mention of when to prefer a guild-scoped listing tool.

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