Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_remove_timeout

Removes a timeout from a Discord member, restoring their ability to send messages and interact in the server. Use it to lift moderation restrictions by guild ID and user ID.

Instructions

Remove a member 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": {
      "guildId": "<guildId>",
      "userId": "<userId>"
    },
    "name": "discord_remove_timeout"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
guildIdYesDiscord id (snowflake)

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?

With no annotations, the description carries the full burden of behavioral disclosure. It implies a mutation but says nothing about required permissions (e.g. Moderate Members), whether the call is idempotent or errors when no timeout exists, or what happens to the audit-log reason.

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?

The single sentence is front-loaded and free of waste, but at six words it is under-specified rather than concise in a helpful sense. It reads more like a title than a usable instruction.

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 annotations, no output schema, and partial parameter documentation, the description is far too thin. It omits permissions, error conditions, and the meaning of the reason field that an agent needs to invoke it correctly.

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%: guildId is documented as a snowflake, userId merely $refs guildId, and the optional 'reason' parameter is undocumented. The description adds no meaning to any parameter, so it fails to compensate for the coverage gap.

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 states a specific verb and resource ('Remove a member timeout'), making the operation and its inverse relationship to discord_timeout_member clear. It stops short of naming the sibling or clarifying scope, but an agent can tell what the tool does without opening the schema.

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 when-to-use guidance, no mention of prerequisites such as an active timeout being present, and no reference to the inverse discord_timeout_member tool. The agent must infer all usage context.

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