Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_timeout_user

Time out a Discord guild member for a set duration in seconds, or pass 0 to remove the timeout.

Instructions

Time out (mute) a guild member for a duration in seconds. Pass 0 to remove the 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>",
      "durationSeconds": "<durationSeconds>"
    },
    "name": "discord_timeout_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
userIdYes
confirmNoSet true to actually perform this destructive action
guildIdYes
durationSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It mentions the action but does not disclose side effects, required permissions, rate limits, or the need for the confirm parameter (which is only hinted in the schema). The behavioral impact of a timeout is not explained.

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 sentence, concise and front-loaded with the core action. However, it omits useful information that could be included without sacrificing conciseness.

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?

With 5 parameters, 3 required, no output schema, and a destructive action, the description is too sparse. It lacks prerequisites, error handling, return value, and permission context.

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 20% (only confirm has a description). The tool description adds context only for durationSeconds (implicitly) but fails to explain reason, userId, guildId, or the confirm parameter's role. No compensation for low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (time out/mute), the resource (guild member), and the duration unit (seconds). It also includes the special case of passing 0 to remove the timeout, distinguishing it from sibling tools like kick or ban.

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 explicit guidance on when to use timeout versus other moderation actions (e.g., kick, ban). The description does not mention alternatives or provide context for decision-making.

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