Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_timeout

Removes a member's timeout in a Discord server, allowing them to send messages and interact again. Supply guild ID, user ID, and optional audit log reason.

Instructions

Remove a member's timeout.

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>"
    },
    "name": "remove_timeout"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason
user_idYes
guild_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it does not say what permissions are needed, whether the audit-log reason is surfaced to the user, or what happens if the member has no active timeout. No contradiction with annotations exists — removing a timeout is restorative, consistent with destructiveHint=false.

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?

A single front-loaded sentence with zero padding, but it is sized for a much simpler tool than this one; the brevity reflects missing content rather than deliberate economy. Nothing in it is wasted, but nothing is added either.

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 mutation tool with no output schema and only partial annotation coverage, the definition leaves out permissions, preconditions (an active timeout must exist), failure behavior, and most parameter meaning. It is not sufficient on its own for an agent to call this correctly without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is only 33%, with guild_id and user_id entirely undocumented, so the description should compensate but does not. It never explains that a guild and target user identify the timeout, nor how the optional reason is used, leaving two of three parameters semantically bare.

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?

"Remove a member's timeout" states a specific verb (remove) and resource (timeout on a member), which is unambiguous and clearly the inverse of a timeout action. It does not name or contrast with the sibling timeout_member, but the purpose itself is not vague or tautological.

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?

There is no guidance on when to use this versus related tools such as timeout_member, nor any mention of prerequisites like required permissions or the guild/user context. The agent must infer the entire usage context from the 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