Skip to main content
Glama
wowjinxy
by wowjinxy

timeout_member

Manage Discord member communication by applying or clearing timeout restrictions to moderate server interactions.

Instructions

Apply or clear a communication timeout for a member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
server_idNo
duration_minutesNo
reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implements the timeout_member tool by fetching the guild and member, calculating timeout duration, applying the timeout, and returning a confirmation message.
    async def handle_timeout_member(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Timeout a member"""
        guild = await discord_client.fetch_guild(int(arguments["server_id"]))
        member = await guild.fetch_member(int(arguments["user_id"]))
        
        duration = timedelta(minutes=arguments["duration_minutes"])
        member_name = member.display_name
        
        await member.timeout(duration, reason=arguments.get("reason", "Timed out via MCP"))
        
        return [TextContent(
            type="text",
            text=f"Timed out member {member_name} for {arguments['duration_minutes']} minutes\nReason: {arguments.get('reason', 'Timed out via MCP')}"
        )]
  • Defines the input schema and parameters for the timeout_member tool during registration.
    Tool(
        name="timeout_member",
        description="Temporarily timeout a member",
        inputSchema={
            "type": "object",
            "properties": {
                "server_id": {"type": "string", "description": "Server ID"},
                "user_id": {"type": "string", "description": "User ID to timeout"},
                "duration_minutes": {"type": "number", "description": "Timeout duration in minutes"},
                "reason": {"type": "string", "description": "Reason for timeout"}
            },
            "required": ["server_id", "user_id", "duration_minutes"]
        }
    ),
  • Dispatches calls to timeout_member (and other advanced tools) by dynamically invoking the corresponding handler method on AdvancedToolHandlers.
    if name in advanced_tool_names:
        handler_method = f"handle_{name}"
        if hasattr(AdvancedToolHandlers, handler_method):
            return await getattr(AdvancedToolHandlers, handler_method)(discord_client, arguments)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool can 'apply or clear' a timeout, implying mutation capabilities, but lacks details on permissions required, whether the action is reversible, rate limits, or what the output contains. This is insufficient for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately front-loaded with the core action, making it easy to parse quickly.

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?

Given the tool's complexity (a mutation tool with 4 parameters, 0% schema coverage, and no annotations), the description is inadequate. It lacks details on parameter usage, behavioral traits, and output expectations, even though an output schema exists. For a tool that modifies member states, more context is needed to guide safe and effective use.

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 0%, so the description must compensate for undocumented parameters. It adds no information about the four parameters (user_id, server_id, duration_minutes, reason), such as how they interact (e.g., null duration_minutes might clear a timeout) or their formats. This leaves the agent reliant solely on the schema's basic titles.

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 clearly states the action ('Apply or clear') and target ('communication timeout for a member'), making the purpose understandable. However, it doesn't differentiate this tool from similar sibling tools like 'ban_member', 'kick_member', or 'moderate_message', which also involve member restrictions.

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 guidance is provided on when to use this tool versus alternatives like 'ban_member' or 'kick_member'. The description mentions both applying and clearing timeouts but doesn't specify scenarios or prerequisites for either action, leaving the agent to infer usage from context alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wowjinxy/mcp-discord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server