Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

preview_app_authorization

Read-only

Preview an OAuth2 authorization before adding a bot to a server; see the app, requested scopes, and eligible servers to confirm the install.

Instructions

Preview an OAuth2 authorization (e.g. adding a bot to a server): shows the app, scopes and servers you can add it to. [GET /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": "preview_app_authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesSpace-separated scopes, e.g. "bot applications.commands"
stateNostate
client_idYesclient id (ID)
permissionsNoPermissions: bitfield string, or names like ["VIEW_CHANNEL","SEND_MESSAGES"]
redirect_uriNoredirect uri
response_typeNoresponse type
integration_typeNo0 server install, 1 user install

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 readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds genuine value by saying what the preview returns (app, scopes, addable servers) and the underlying GET route, but omits permissions/scoping prerequisites and whether the preview result must be echoed back to authorize_app.

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?

One tight sentence plus a bracketed endpoint tag, front-loaded with the core action. Nothing is wasteful, though the endpoint tag is arguably boilerplate rather than agent-facing guidance.

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 read-only GET with a fully described 7-parameter schema and no output schema, the definition covers purpose, example context, and return content well enough to call it correctly. The remaining gap is the relationship to the authorize step, which is a routing concern more than a completeness one.

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 description coverage is 100%, so all seven parameters (scope, client_id, permissions, redirect_uri, response_type, integration_type, state) are already documented. The description only alludes to 'scopes' and adds no format or interaction detail (e.g. permissions requiring the bot scope, server vs user install via integration_type), so 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?

The description gives a specific verb+resource ('Preview an OAuth2 authorization') and clarifies the payload with a concrete example ('adding a bot to a server') plus what is displayed (app, scopes, servers). It stops short of explicitly contrasting with the sibling 'authorize_app', so an agent must infer that this one does not commit the 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 word 'Preview' and the read-only framing imply this is a pre-flight/inspection call, but the description never states when to use it versus authorize_app, nor any prerequisites (valid client_id, authenticated user). Usage is implied rather than spelled out.

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