Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

authorize_app

Authorize a Discord app via OAuth2 to add a bot to a server or install a user app, defining scopes, guild ID, permissions, and integration type.

Instructions

Authorize an app — e.g. add a bot to a server (scope "bot applications.commands", guild_id, permissions) or install a user app (integration_type 1). [POST /oauth2/authorize]

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": {
      "client_id": "<client_id>",
      "scope": "<scope>"
    },
    "name": "authorize_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesSpace-separated scopes
stateNostate
guild_idNoServer (guild) ID
authorizeNoauthorize
client_idYesclient id (ID)
dm_settingsNodm settings
permissionsNoPermissions: bitfield string, or names like ["VIEW_CHANNEL","SEND_MESSAGES"]
redirect_uriNoredirect uri
response_typeNoresponse type
integration_typeNointegration type
location_contextNolocation context
webhook_channel_idNowebhook channel id (ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.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 operation. The description adds useful outcome context—adding a bot or installing a user app—but does not disclose required permissions, side effects, redirect behavior, or reversibility.

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?

A single front-loaded sentence with compact parenthetical examples and the endpoint. No filler or repetition; every element contributes to selecting the correct mode.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 12 parameters, nested objects, open-world behavior, and no output schema, so the description needs to orient the agent. It identifies the two main authorization modes and the endpoint, but omits redirect/state handling, authorization prerequisites, and what happens after the call, leaving gaps for a complex OAuth flow.

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?

Schema coverage is 100%, so the schema already documents all 12 parameters. The description adds meaning by showing concrete parameter combinations for the two modes, including scope 'bot applications.commands', guild_id, permissions, and integration_type 1, though it does not explain the remaining parameters.

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?

The description states a specific verb and resource ('Authorize an app') and gives two concrete modes: adding a bot to a server and installing a user app. It is clearly not a tautology, but it does not explicitly differentiate itself from siblings such as deauthorize_app or preview_app_authorization.

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?

The description gives two concrete examples (adding a bot to a server and installing a user app), which establishes clear usage context. However it does not state when to choose this over preview_app_authorization or deauthorize_app, nor any prerequisites or exclusions, so guidance remains implied rather than explicit.

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