Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user_command_index

Read-only

Retrieves the command index for your installed applications, listing available app commands so you can discover and invoke them through Discord.

Instructions

Commands of user-installed apps. [GET /users/@me/application-command-index]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 nothing beyond them — no indication of whether the result is paginated, how large the index can be, or whether it only reflects apps the user has installed — so the bar to clear was low and it was not cleared.

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, front-loaded, with no filler. The bracketed endpoint notation is arguably redundant for an agent but costs little and is at least clearly delimited.

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 zero-parameter read-only lookup, the annotations carry the safety profile and the empty schema removes ambiguity about inputs, so little is strictly missing. However, the agent still cannot tell what shape the returned command index has or how this differs from the three sibling index endpoints, which is the one thing a description of this tool should settle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline is 4 and there is nothing for the description to document. The bracketed HTTP route is mild extra context but not parameter semantics.

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

Purpose3/5

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

The phrase 'Commands of user-installed apps' names the resource and implicitly scopes it to the current user, which loosely distinguishes it from the guild/channel/app command-index siblings. But it is a noun fragment with no verb ('list'/'get') and never states that it returns commands, leaving the agent to infer the action from the tool name.

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 mention of prerequisites, and no reference to the sibling command-index tools (get_guild_command_index, get_channel_command_index, get_app_command_index). The only hint is the implicit 'user-installed apps' scoping, which the agent must decode on its own.

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