Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_channels

Read-onlyIdempotent

Lists all channels in a Discord guild by guild ID, with optional bot token authentication when not connected through UnClick.

Instructions

List channels in a Discord guild.

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

Input Schema

NameRequiredDescriptionDefault
guild_idYes
bot_tokenNoBot token. Optional when connected in UnClick or the documented env var is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • addedInput schema / properties / bot_token / description
      Added value: +"Bot token. Optional when connected in UnClick or the documented env var is set."
    • changedInput schema / required
      Previous value: -[
-  "bot_token",
-  "guild_id"
-]New value: +[
+  "guild_id"
+]
  2. Addedv0.1.5

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds no behavioral context beyond the purpose itself, such as pagination, ordering, channel types returned, 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.

Conciseness5/5

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

The description is a single, front-loaded sentence with no redundant or filler content. It is appropriately sized for a simple list operation, even though it omits details covered under other dimensions.

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 simple read-only listing tool, the description leaves important gaps: it does not explain the format of guild_id, what channel fields are returned, whether pagination is needed, or which channel types are included. With no output schema present, the description should do more to set expectations about the result.

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?

The schema description coverage is only 50%, and the required guild_id parameter has no description in the schema. The tool description also adds no format or meaning for guild_id or bot_token, so the agent receives little help on how to supply the critical required parameter.

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 and resource: list channels in a Discord guild. It is clear enough to distinguish from sibling tools like discord_members or discord_send, though it does not explicitly mention those alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives such as discord_search or discord_members. It only implies usage through the purpose statement, leaving the agent to infer context.

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