Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_command_index

Read-only

Retrieves all slash and context commands available in a Discord server with application info, enabling discovery and correct execution of server commands.

Instructions

All slash/context commands available in a server (with application info). run_slash_command uses this for you. [GET /guilds/{guild_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": {
      "guild_id": "<guild_id>"
    },
    "name": "get_guild_command_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only the content note 'with application info' — no word on permissions required, pagination, or result ordering, which is modest added value over the annotations.

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 sentences plus an endpoint reference, with the resource scope front-loaded and the usage hint immediately after. Nothing is padded, though the bracketed HTTP path is only marginally useful to an agent.

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

Completeness4/5

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

For a one-parameter read-only lookup with no output schema, the definition covers what is returned (all slash/context commands, with application info) and how it is normally consumed. Missing return-shape or volume details are minor given the annotations and absent output schema.

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?

With a single parameter and 100% schema description coverage, the schema fully documents guild_id ('Server (guild) ID'). The description adds no format hints or constraints beyond that, so the baseline of 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 names a specific resource (all slash/context commands available in a server) and adds scope detail ('with application info'), plus the underlying endpoint. 'Available in a server' implicitly marks it as the guild-wide index, which separates it from the channel/user-scoped siblings, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear alternative path: 'run_slash_command uses this for you,' telling the agent this is usually reached indirectly. What is missing is an explicit statement of when an agent should call it directly (e.g., discovery/listing use cases) versus deferring to run_slash_command.

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