Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_join_request_cooldown

Read-only

Retrieve the cooldown for your join request in a Discord server to know when you can request to join again.

Instructions

Get Guild Join Request Cooldown. [GET /guilds/{guild_id}/requests/@me/cooldown]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "get_guild_join_request_cooldown"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds nothing beyond that — no statement of what the cooldown means (remaining seconds, eligibility window), whether it errors when no request exists, or any rate/auth context.

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?

It is very short with no waste, but the brevity comes from under-specification rather than tight writing. The bracketed endpoint is the only content beyond the title and adds marginal value.

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 no output schema, the description bears full responsibility for explaining what is returned — e.g. a cooldown timestamp or remaining duration — and it says nothing. For a read tool whose entire purpose is producing a value, that omission leaves an agent unable to interpret the response.

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

Parameters3/5

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

Schema description coverage is 100% with a single required guild_id documented as 'Server (guild) ID', so the schema already carries the meaning. The description contributes no additional parameter semantics; baseline 3 applies.

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

Purpose2/5

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

The description is essentially the tool name plus a bracketed HTTP path; it restates 'Get Guild Join Request Cooldown' without explaining what a cooldown value is or what it is measured against. The endpoint path [/guilds/{guild_id}/requests/@me/cooldown] does hint that the result is scoped to the calling user (@me), which is a small piece of added meaning, but no sibling differentiation or scope statement is provided.

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 at all — no mention of when an agent should check the cooldown versus calling the join-request action tools (create/action/reset_guild_join_request) that are clearly adjacent. Nothing indicates prerequisites such as having a pending join request.

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