Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_join_request

Destructive

Cancel your pending request to join a Discord server by deleting the join request for the specified guild ID.

Instructions

Delete Guild Join Request. [DELETE /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": "delete_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHandle, so the safety profile is covered elsewhere. The description adds only the underlying HTTP endpoint; it says nothing about whether the request can be re-created afterwards, whether a cooldown applies, or what the response contains.

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?

A single front-loaded line plus the route, with zero filler. It is efficient, though the bracketed path is largely redundant with what the name and schema already convey.

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 one-parameter destructive delete with full schema coverage, explicit destructive annotations, and no output schema, next to nothing else is required. The only meaningful gap is post-deletion behavior such as re-request or cooldown semantics.

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 coverage is 100% and the single guild_id parameter is fully documented as "Server (guild) ID". The route template corroborates its position in the path but adds no new meaning, so the baseline 3 is appropriate.

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?

States a specific verb and resource ("Delete Guild Join Request") and the bracketed route pins the scope to the caller's own request via the @me path segment, which separates it from the sibling list/action tools. It stops short of naming a specific sibling as an alternative, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the @me route indicates this cancels your own pending join request, while sibling tools like action_guild_join_request handle other users' requests. The description never explicitly says when to use this versus those alternatives or what preconditions apply.

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