Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_app_command_index

Read-only

Retrieves the application command index for a Discord application by ID, helping identify and manage the commands available to that app or bot.

Instructions

Get Application Command Index. [GET /applications/{application_id}/application-command-index]

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

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/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 structurally. The description adds nothing beyond that: no note on permissions/bot-scope requirements, rate limits, or whether the index is scoped to the calling app versus the target application_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, so nothing is wasted, but the brevity comes from under-specification rather than economy. The bracketed route is the only informative content.

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

Completeness2/5

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

For a single-parameter read tool this could be adequate, but the term "command index" is undefined and the description never clarifies the relationship between the index and the individual command endpoints. No output schema exists to compensate.

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?

Only one parameter, and the schema fully documents it ("Application (app/bot) ID") at 100% coverage. The description adds no extra meaning, but per the baseline rule for complete schema coverage, 3 is the ceiling here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name verbatim ("Get Application Command Index") and appends the raw HTTP route. Neither explains what an "application command index" actually is or what the call returns (a list of commands, metadata, counts). Without the route string it would be pure tautology.

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 statement of when to use this instead of the many nearby siblings (get_global_application_command, get_guild_application_command, get_guild_command_index, get_channel_command_index). The agent must infer scope from the endpoint path 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