Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_authorized_apps

Read-only

Lists the third-party applications you have authorized with your Discord account, helping you review and audit OAuth2 access tokens.

Instructions

Apps you have authorized with your account (Settings → Authorized Apps). [GET /oauth2/tokens]

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

Input Schema

NameRequiredDescriptionDefault
application_idsNoapplication ids

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 readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds the underlying endpoint [GET /oauth2/tokens], which hints that the data comes from the user's OAuth2 token grants, but says nothing about pagination, result size, or which scopes/tokens are surfaced.

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 fragments with the core scope front-loaded and no filler. The bracketed endpoint is developer-oriented and slightly at odds with the user-facing Settings anchor, but it is not wasteful.

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?

With no output schema, the description does most of the work by stating that the result is the set of authorized apps, but it omits return shape, pagination behavior, and the meaning of the single optional filter. Adequate for a simple read tool, not complete.

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%, so the baseline is 3, but the sole parameter application_ids is documented only as 'application ids', and the description does not explain that it acts as a filter or what happens when it is omitted. The description neither compensates for nor worsens the thin schema text.

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 names the specific resource and its scope: apps the *calling user* has authorized on their own account, with a human-readable anchor (Settings → Authorized Apps). That scope distinguishes it from broad siblings like list_applications or list_app_directory_categories, though it never names a sibling explicitly.

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 when-to-use guidance, no statement of prerequisites or auth requirements, and no exclusion pointing to alternatives such as get_authorized_app for a single app. The Settings path is a UI pointer, not routing guidance.

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