discord_list_rolesList all roles in a Discord guild by providing the guild ID to inspect permissions, hierarchy, and member assignments for management or backup.
List roles in a Discord guild.
| Name | Required | Description | Default |
|---|---|---|---|
| guildId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| error | No |
Changes observed during successful MCP inspections.
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 fully covered. The description adds nothing beyond that — no note on pagination, ordering, permission requirements, or the open-world/network nature of the call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero waste. However, the brevity tips into under-specification rather than optimal conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and annotations cover safety. But the lone required parameter's meaning is undocumented anywhere, leaving a real gap for an agent trying to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single guildId parameter has 0% schema description coverage — only a regex pattern is given. The description does not explain that guildId is the target guild's snowflake ID or how to obtain it, so it fails to compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb ('List') and resource ('roles in a Discord guild'), so an agent knows exactly what it returns. It does not explicitly contrast with siblings like discord_get_role or discord_list_role_member_counts, keeping it below a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 versus discord_get_role, discord_list_role_member_counts, or the role-mutation tools. The agent must infer the context 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.
This server cannot be deployed