Retrieve detailed information for a specific Discord role using its role ID, optionally scoped to a guild for context.
Get detailed information about a specific role
| Name | Required | Description | Default |
|---|---|---|---|
| roleId | Yes | Role ID | |
| guildId | No | Discord server ID (defaults to DISCORD_GUILD_ID) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read but never states whether it requires permissions, how it behaves when roleId is invalid, or what 'detailed information' comprises.
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 tight sentence with no waste, though its brevity comes at the cost of substance rather than being efficient prioritization.
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?
For a lookup tool with no output schema and no annotations, the description should say what detail is returned and any permission or scope caveats. 'Detailed information' leaves the agent guessing about the response.
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?
Schema coverage is 100%, so roleId and the guildId default are fully documented in the schema. The description adds nothing beyond that, which is the expected baseline when the schema does the work.
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+resource (get + role), but 'detailed information' is vague about what is returned, and nothing distinguishes it from siblings like list_roles, get_member_info, or get_channel_info.
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?
No when-to-use guidance, no prerequisites, and no mention of alternatives such as list_roles when the agent wants many roles rather than one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.