Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

timeout_member

Destructive

Temporarily prevent a Discord member from chatting or joining voice for a specified number of minutes, up to 28 days, using guild ID, user ID, and duration.

Instructions

Time out a member (they cannot chat or join voice) for N minutes (max 40320 = 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": {
      "guild_id": "<guild_id>",
      "user_id": "<user_id>",
      "minutes": "<minutes>"
    },
    "name": "timeout_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
minutesYesDuration in minutes
user_idYes
guild_idYes

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?

Annotations already flag this as a destructive, open-world write, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the concrete effect of the timeout and the hard ceiling of 40320 minutes (28 days). It does not mention required permissions, whether an existing timeout is replaced or extended, or what happens to a member already timed out.

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?

A single compact sentence, front-loaded with the action and followed by the effect and the constraint. No filler, though the nested parentheticals make it slightly denser than necessary.

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 destructive four-parameter moderation tool with no output schema, the description covers the core action and the duration cap but omits permission requirements and the interaction with pre-existing timeouts. It is adequate to invoke the tool, but not complete for a mutation of this consequence.

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%, and the description compensates for part of that by pinning down the `minutes` parameter's range and unit (N minutes, max 40320 = 28 days), which the schema's bare 'Duration in minutes' does not. The remaining required parameters (guild_id, user_id) and the optional `reason` audit-log field are left entirely to the schema.

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?

States a specific verb and resource (time out a member) and immediately defines the concrete effect on the member (cannot chat or join voice), so an agent can distinguish it from siblings like remove_timeout or ban_member. It never names those alternatives explicitly, which keeps it just short of a 5.

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 gives no explicit when-to-use or when-not-to-use guidance. There is no routing toward kick_member, ban_member, or remove_timeout when a timeout is not the right moderation action, leaving the agent to infer the choice of tool.

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