Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

reset_guild_join_request

Reset a pending join request for a Discord server using its guild ID, clearing the prior request so you can submit a new one.

Instructions

Reset Guild Join Request. [POST /guilds/{guild_id}/requests/@me]

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": "reset_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world call, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the `@me` path segment reveals it operates on the authenticated user's own request rather than another member's. It says nothing, however, about whether resetting re-sends the request, is idempotent, or is subject to cooldowns.

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?

Two terse segments with no filler and the resource named up front. The bracketed route is compact and useful; the only weakness is that the terseness shades into under-specification rather than efficient communication.

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?

For a POST mutation with no output schema and only partially informative annotations, the description should explain what resetting actually does and what state results. Instead it leaves the core effect of the operation undefined, which is the main thing an agent needs before calling a write tool.

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?

The single `guild_id` parameter is fully documented in the schema (100% coverage), so the baseline of 3 applies. The description adds no further meaning about the parameter beyond what the schema already states.

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 first sentence, "Reset Guild Join Request," simply restates the tool name without explaining what "reset" does to the request. The bracketed endpoint adds some specificity by showing the target is the current user's own request (`requests/@me`), but the verb itself is never clarified, and no sibling (create_guild_join_request, delete_guild_join_request, action_guild_join_request) is distinguished.

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, no precondition, and no mention of the closely-named alternatives. An agent cannot tell from this text whether to reset, create, delete, or action a 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