Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_authorized_app

Read-only

Retrieve the OAuth2 application authorized by a specific Discord token ID to identify which app has access.

Instructions

Get OAuth2 Authorization. [GET /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": "get_authorized_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesAuthorization (OAuth2 token) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds the endpoint path but does not disclose authentication requirements, failure behavior, rate limits, or any other behavioral context beyond what the annotations provide.

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?

The description is two short, front-loaded statements with no wasted wording. The endpoint is presented compactly as an additional routing detail.

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?

For a simple, one-parameter read tool with full schema coverage and meaningful annotations, the description is minimally adequate. However, with no output schema, it omits any indication of what authorization details are returned, leaving a gap for the caller.

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 token_id is already documented as the OAuth2 token ID. The description repeats the endpoint path variable but adds no additional meaning about accepted formats or lookup behavior.

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: retrieve an OAuth2 authorization by token ID. The HTTP endpoint reinforces that this is a single-token lookup, distinguishing it from list_authorized_apps, though it does not explicitly name alternatives.

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 guidance on when to use this tool versus list_authorized_apps or authorization-related siblings. The required token_id implies a single-record retrieval, but the description provides no stated usage conditions or exclusions.

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