Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove timeout

remove_timeout

Lift a member's active timeout early with a preview-and-confirm step, restoring their ability to chat; no change is made if no timeout is active.

Instructions

Lift an active timeout from a member early. It puts someone a moderator silenced back in the conversation, so it needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. A member who is not timed out is left alone, with nothing to confirm.

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

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
memberYesMember name or user ID.
reasonNo
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, which only say readOnlyHint=false and destructiveHint=false, the description discloses the full two-phase confirmation protocol: the first call changes nothing and returns a preview and a confirm_token, and the second call makes the change. It also discloses the no-op behavior for members who are not timed out. That is exactly the kind of behavior an agent needs in order to plan around it.

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?

Three short sentences, each essential: purpose, confirmation flow, and edge-case behavior. It is front-loaded with the action and wastes no words.

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 mutation tool with no output schema, it covers the confirmation lifecycle and the non-timed-out edge case well. It omits the permission requirements, such as the moderator role needed to lift a timeout, and never explains the purpose of the reason field.

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 schema describes three of the four parameters and fully covers confirm_token. The description still adds value by explaining where the token comes from and when to supply it during the workflow, which is more than the schema's static text conveys. The reason parameter still gets no explanation beyond the schema.

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 opens with a precise verb and resource: 'Lift an active timeout from a member early.' That statement is specific enough for an agent to tell this apart from its sibling timeout_member, which applies a timeout rather than lifting one. The word 'early' adds a useful scope qualifier.

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 clearly explains the scenario that should trigger the tool and what happens when the member is not timed out ('left alone, with nothing to confirm'), so an agent knows it is safe to call in that case. It does not name an alternative tool or list exclusions, so it does not reach the level of a 5.

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