Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_global_application_commands

Read-only

Fetches the global application commands for a Discord app by application ID, optionally including localizations, to inspect slash commands registered app-wide.

Instructions

List Global Application Commands. [GET /applications/{application_id}/commands]

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": {
      "application_id": "<application_id>"
    },
    "name": "list_global_application_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication (app/bot) ID
with_localizationsNowith localizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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. The description adds only the raw HTTP endpoint, which largely restates the resource and reveals nothing extra about return size, pagination, or scope behavior.

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?

It is two short fragments with zero padding and the purpose is front-loaded. Nothing is wasted, though the terseness leaves no room for the guidance a list tool with several siblings would benefit from.

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 two-parameter read tool with no output schema, the definition is minimally sufficient; return values need not be described. However, it says nothing about result scope or whether the listing is paginated, which an agent calling it would want to know.

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 both application_id and with_localizations are already documented in the schema. The description adds no meaning beyond it; 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 clear verb+resource ('List Global Application Commands'), and the 'Global' qualifier implicitly separates it from the guild-scoped siblings. It does not explicitly name an alternative, but the resource and scope are 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?

There is no guidance on when to use this tool versus list_guild_application_commands or list_commands, and no prerequisites or exclusions are stated. The agent must infer selection from the name 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