Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

deauthorize_app

Destructive

Revoke an OAuth2 app's access to a Discord account by deleting its authorization token using the token ID.

Instructions

Revoke an app's access to your account. [DELETE /oauth2/tokens/{token_id}]

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": {
      "token_id": "<token_id>"
    },
    "name": "deauthorize_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesAuthorization (OAuth2 token) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 adds the underlying operation (DELETE /oauth2/tokens/{token_id}), which confirms the token is permanently removed and hints at the resource path. It does not say whether the effect is reversible for the user or whether the app itself is notified.

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 short clauses with the action front-loaded and no filler. The bracketed HTTP route is marginal value for an agent that doesn't issue raw HTTP, but it does disambiguate the operation.

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 single-parameter destructive tool with no output schema and full annotation coverage, the definition gives enough to call it correctly. The remaining gap is post-call behavior and any authorization prerequisite, which are not described.

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 parameter is already described as 'Authorization (OAuth2 token) ID'. The description only mirrors that token_id maps into the DELETE path, adding no new constraint, format, or sourcing guidance (e.g., where to obtain the token ID). Baseline 3 applies.

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?

Uses a specific verb+resource ('Revoke an app's access to your account') and the inverted operation is obviously the sibling 'authorize_app', so an agent can distinguish intent. It stops short of naming the sibling explicitly, but the action is unambiguous.

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?

No when-to-use or when-not-to-use guidance beyond the bare action; it doesn't mention that this is the inverse of authorize_app or that the app can simply be re-authorized. The agent must infer the trigger condition from the verb alone.

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