Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_members

Read-onlyIdempotent

Retrieves a list of members from a Discord guild using its guild ID, with an optional limit and bot token for authentication.

Instructions

List members of 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_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
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.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds almost no behavioral context beyond the basic purpose: it does not mention pagination, rate limits, required permissions, or whether results are filtered or complete.

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?

The description is one front-loaded sentence with no wasted words. It is appropriately concise, though the brevity contributes to the gaps in other dimensions rather than being a structural flaw.

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 tool with no output schema and low schema coverage, the description is too thin. It does not explain the limit behavior, guild_id requirements, or what the returned member list contains, leaving meaningful gaps for an agent to call it correctly.

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 only 33%, with just bot_token documented. The description does not explain guild_id format or the meaning, default, or maximum of limit, so it fails to compensate for the undocumented parameters.

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 gives a specific verb and resource ('List members of a Discord guild'), so an agent can distinguish it from message-oriented siblings like discord_read and discord_search. It does not explicitly differentiate from discord_channels, but the resource is clear enough to identify the operation.

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 tool instead of siblings such as discord_search, discord_read, or discord_channels. No prerequisites, authentication context, or exclusions are stated, leaving the agent to infer usage from the name alone.

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