Discord MCP Server and API by Cotlet

Time out member in Discord

discord_time_out_member

Read-onlyIdempotent

Time out member in the user's own Discord account from ChatGPT, Claude or any AI agent. Returns how to do it in Discord step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Discord Cloud Browser. Discord's official API: Yes, Discord has an official API for bots and OAuth2 apps, but it acts as a bot that a server manager adds, not as you, and Discord has no official MCP server for it (checked 5 Nov 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_time_out_member"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that by stating it 'opens nothing by itself'. It adds genuinely useful behavior the annotations cannot convey: the return value is step-by-step Discord UI instructions (screens, buttons, fields), and the actual execution requires the Discord Cloud Browser plus cotlet_browser_* tools.

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 core purpose and the browser follow-up are front-loaded and clear, but the closing sentence about Discord's official API and the 'checked 5 Nov 2026' metadata is tangential justification that does not help an agent invoke the tool. Some of the phrasing ('from ChatGPT, Claude or any AI agent') is marketing filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter guidance tool with no output schema, the description covers what it returns (ordered UI steps), what it does not do (open anything or act on the account), and the required companion toolset. It leaves the handoff to the browser tools somewhat underspecified but is otherwise sufficient to invoke correctly.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty at 100% coverage, so the baseline is 4. One could argue the description should explain why no member/server identifier is accepted, but with no parameters to misinterpret this is a minor gap.

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 states a specific verb+resource ('Time out member in the user's own Discord account') and immediately clarifies the actual mechanism: it returns step-by-step instructions rather than performing the action. That distinction separates it from an action-performing tool and from siblings like discord_assign_role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says this tool returns guidance and 'opens nothing by itself', then directs the agent to 'do it with the cotlet_browser_* tools in the user's Discord Cloud Browser', giving a clear follow-up path. It also justifies why the official Discord API is not used. It does not name the other discord_* siblings or state when those would be preferable.

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

All Discord MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?