Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_application_command

Read-only

Retrieves a specific guild application command using application, guild, and command IDs to inspect its configuration or details.

Instructions

Get Guild Application Command. [GET /applications/{application_id}/guilds/{guild_id}/commands/{command_id}]

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>",
      "command_id": "<command_id>"
    },
    "name": "get_guild_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
command_idYesApplication command ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 endpoint path, with no additional context about auth requirements, rate limits, or what happens when the command or guild does not exist.

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, front-loaded clauses with no filler: the name followed by the endpoint template. It is efficient, though the endpoint bracket adds only marginal value over the title.

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 three-parameter read tool with full schema coverage and complete annotations, the description is adequate but minimal. It lacks any note on error behavior or distinction from the many sibling get_* commands, which is the main residual gap.

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%, with application_id, guild_id, and command_id each documented in the schema. The description's URL template merely maps those same IDs into their path positions and adds no semantics beyond what the schema already provides, so baseline 3 applies.

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 and adds the HTTP route, which does signal guild-scoped (rather than global) command retrieval. However, it never explicitly contrasts itself with get_global_application_command or list_guild_application_commands, so the agent must infer the distinction from the endpoint template.

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 prerequisites, and no mention of alternatives. The agent is left to deduce from the name and URL path that this fetches a single guild-scoped command by ID rather than listing or fetching a global 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