Skip to main content
Glama
discord-mcp-lite

discord-mcp-lite

find_channel

Read-only

Search Discord channels by case-insensitive name substring across all guilds or within one guild to quickly locate channels for read-only message history access.

Instructions

Find channels by name (case-insensitive substring). Searches every guild when guild_id is omitted.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPart of a channel name, e.g. "tax".
guild_idNoOptional: restrict the search to one guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It contributes the default cross-guild search behavior, but says nothing about result limits, ordering, or whether partial matches are capped, which matters when searching across every guild.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the primary matching behavior is front-loaded ahead of the scope default. Every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with fully documented params and no output schema, the definition covers purpose, matching semantics, and scope default. The only remaining gap is what a match returns and whether results are bounded.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it clarifies that query is a case-insensitive substring and that omitting guild_id widens scope to all guilds rather than erroring or defaulting. That default-behavior detail is not stated in the schema.

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 matching mechanism (case-insensitive substring), so the agent knows this is a lookup rather than an enumeration. It does not explicitly contrast itself with the sibling list_channels, but the matching semantics are distinctive enough to separate the two.

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 "Searches every guild when guild_id is omitted" implies the scoping choice an agent faces, but there is no explicit when-to-use/when-not guidance and no named alternative such as list_channels for full enumeration. Usage is inferable rather than stated.

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