Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_application_commands

Read-only

Fetches the application commands for a specified Discord application and guild, letting you inspect available slash commands and optional localizations.

Instructions

List Guild Application Commands. [GET /applications/{application_id}/guilds/{guild_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>",
      "guild_id": "<guild_id>"
    },
    "name": "list_guild_application_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
application_idYesApplication (app/bot) ID
with_localizationsNowith localizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds only the endpoint path; it says nothing about pagination, ordering, permissions the bot needs, or whether the returned commands include guild-scoped overrides.

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, but it wastes one of its two sentences on an HTTP path that adds no decision-relevant information, while leaving out details an agent would actually need.

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 read-only list endpoint with a fully documented schema and annotations, the minimum is covered. However, there is no output schema, so the description should say what is returned (array of command objects) and whether results are paginated, which it does not.

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 all three parameters are documented in the schema and the baseline of 3 applies. The description adds no meaning beyond the schema and does not clarify the vague 'with localizations' flag.

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 description restates the tool name verbatim ('List Guild Application Commands') and adds only the HTTP path. It does not explain what a guild application command is or how this differs from the sibling list_global_application_commands; the guild/global distinction is left entirely to the reader's inference from the 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 or when-not-to-use guidance. No mention of when a caller should choose this over list_global_application_commands or list_commands, and no prerequisites such as needing the bot to be in the guild.

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