Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_timeout_member

Puts a Discord server member in timeout for a specified number of minutes, up to 28 days, to restrict their activity; requires the Moderate Members permission.

Instructions

Put a member in timeout. Requires Moderate Members. Maximum 28 days.

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>",
      "userId": "<userId>",
      "minutes": "<minutes>"
    },
    "name": "discord_timeout_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)
minutesYesTimeout length in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key permission gate (Moderate Members) and the 28-day cap, which is real value. It is silent on whether a new timeout replaces or extends an existing one, whether the member must currently be in the guild, and what happens on failure — meaningful gaps for a moderation mutation.

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?

Three short sentences, action first, constraint last, with no filler. Appropriate size for the information conveyed, though the sentence order could be tightened by pairing the permission requirement with the action.

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 four-parameter destructive moderation tool with no annotations and no output schema, the description covers the essentials of what it does and who may call it. It does not cover overwrite semantics, failure modes, or what the call returns, which an agent needs before mutating a member's state.

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 50%: guildId and minutes are described, while userId and reason are not (userId is a bare $ref to the guildId property). The description's 'Maximum 28 days' merely restates the schema's maximum of 40320 minutes and adds nothing about the reason field or the semantics of replacing an active timeout. Baseline 3 is appropriate given partial schema documentation.

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?

Specific verb and resource: 'Put a member in timeout' unambiguously names the action and target, and it contrasts implicitly with sibling discord_remove_timeout. It does not explicitly name the inverse tool, so the differentiation is left to inference.

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?

The description says nothing about when to choose this over discord_ban_member, discord_kick_member, or discord_remove_timeout. 'Requires Moderate Members' is a permission prerequisite, not usage guidance, so the agent gets no routing criteria beyond the tool's own name.

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