TheeDiscordMCP

by TheETR

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

discord_automod

List, create, modify, or delete Discord AutoMod rules to enforce server moderation policies.

Instructions

List, create, modify, or delete Discord AutoMod rules.

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": {
      "guildId": "<guildId>",
      "action": "<action>"
    },
    "name": "discord_automod"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No
`action`	Yes
`dryRun`	No
`reason`	No
`ruleId`	No
`confirm`	No
`guildId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description must convey safety and side effects. It implies mutation via create/delete but does not mention permission requirements, dry-run behavior, confirmation steps, irreversibility, or any system impact. The schema's dryRun and confirm flags are not referenced.

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 a single, grammatically clean sentence with no wasted words. However, it is under-specified given the tool's complexity, yet it remains concise as a standalone statement.

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

Completeness1/5

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

With 7 parameters, a nested body object, no annotations, and no output schema, the one-line description is wholly inadequate. It does not explain parameter interactions, response format, safety mechanisms, or operational requirements, leaving the agent without sufficient context to invoke the tool correctly.

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 0%, and the description adds no meaning to any of the 7 parameters. It only repeats the action enum values already present in the schema. No explanation of body, ruleId, guildId, or confirm is provided.

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 clearly states the tool's purpose: managing Discord AutoMod rules via list, create, modify, or delete operations. It names a specific resource and verb, though it does not explicitly differentiate from sibling tools beyond the unique resource identifier.

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 is given on when to use this tool vs. alternatives, nor any context for selecting an action. The description lists operations but lacks prerequisites, exclusions, or situational cues.

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