Skip to main content
Glama
Sys0xdbg

better-discord-mcp

by Sys0xdbg

discord_delete_automod_rule

Remove a Discord AutoMod rule by providing its guild and rule ID, requiring explicit confirmation to execute the deletion.

Instructions

Delete an AutoMod rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleIdYes
confirmNoSet true to actually perform this destructive action
guildIdYes
Behavior2/5

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

No annotations are provided, so the description must carry the burden of disclosure. It merely states 'Delete' but does not elaborate on destructiveness, irreversibility, permissions, or side effects beyond what the confirm parameter implies (which is in the schema).

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. It front-loads the action, but omits parameter details or behavioral context, making it too sparse.

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 destructive action with no output schema and low schema documentation, the description should explain what the ruleId and guildId refer to, and any necessary permissions. It fails to provide this context, leaving the tool incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only confirm has a description). The tool description adds no parameter information; guildId and ruleId are undefined in both the description and schema, leaving the agent to guess their format and origin.

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 'Delete an AutoMod rule' clearly states the verb and resource. It distinguishes from sibling tools like discord_create_automod_rule and discord_edit_automod_rule, making its purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. The existence of siblings implies usage, but no explicit context is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sys0xdbg/better-discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server