Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

revoke_user_invites

Destructive

Revoke all friend invites sent from your Discord account to cancel pending requests and clear your invite list.

Instructions

Revoke all your friend invites. [DELETE /users/@me/invites]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 openWorldHint=true, so the safety profile is covered. The description's added value is the word 'all', which discloses batch scope (it wipes every pending friend invite, not one). It does not state reversibility or any confirmation requirement, so it is useful but not rich.

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?

Two terse fragments with zero waste: the action is front-loaded and the endpoint follows as supporting detail. Nothing is padded or repetitive.

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 destructive call whose annotations already cover the safety profile, the definition covers what is being destroyed and at what scope. It could be slightly clearer about whose invites (sent vs. received) are revoked, which is the one ambiguity an agent might hit.

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, so the schema carries no semantics to compensate for and the baseline is 4. The description appropriately says nothing about inputs because there are none.

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+resource pair ('Revoke ... friend invites') and adds the backing endpoint (DELETE /users/@me/invites), which pins down exactly what is being removed. It is clearly distinguishable from the listing/creating invite siblings by verb, though it does not name them.

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 explicit when-to-use guidance and no mention of alternatives such as removing a single invite or listing invites first. The bulk 'all' phrasing implies this is a blanket cleanup rather than a targeted removal, but that is left for the agent to infer.

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