Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List AutoMod rules

list_automod_rules
Read-only

Lists a Discord server's automatic moderation rules and explains what each rule does; optionally target a specific guild.

Instructions

Server-side automatic moderation rules and what they do.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_automod_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description's burden is lower. It adds a small amount by implying the response includes each rule's behavior ('what they do') and that rules are server-side scoped, but says nothing about pagination, completeness of the listing, or what happens when there are no rules.

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?

It is a single short fragment with no filler, but it is under-specified rather than genuinely concise - the missing verb is exactly what an agent needs first. A front-loaded 'Lists...' clause would have cost one word and removed the ambiguity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read with an annotation-declared safety profile and no output schema, the definition is close to sufficient. The gaps are that it never confirms what fields a rule exposes or whether the listing is exhaustive for the guild.

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

Parameters3/5

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

Schema coverage is 100% and the single optional 'guild' parameter is fully documented in the schema (name or ID, omit for default). The description adds no meaning beyond that, which is acceptable given high schema coverage, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (server-side automatic moderation rules) and hints at returned content ('what they do'), but it never states the action - no verb like 'list' or 'retrieve' appears in the description itself. An agent must infer from the tool name that this returns a collection rather than describing a category of rules.

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 versus the obvious CRUD siblings (create_automod_rule, update_automod_rule, delete_automod_rule), and no note that it is a read-only inventory operation. The read-only nature is only inferable from the name and annotations, not from the description.

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