Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_global_application_command

Read-only

Retrieve a global application command's details using its application ID and command ID to inspect or verify the registered slash command configuration.

Instructions

Get Global Application Command. [GET /applications/{application_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>",
      "command_id": "<command_id>"
    },
    "name": "get_global_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYesApplication command ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 that — no mention of required bot/auth scope, whether the command must exist, or what happens for unknown IDs. The endpoint notation is the only extra signal.

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 with zero padding and the resource name front-loaded. It is terse rather than bloated, though the terseness comes at the cost of information rather than in service of it.

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 two-parameter read tool whose annotations carry the safety profile, this is minimally sufficient to invoke correctly. However, with no output schema, the description does not indicate what a command object contains or how errors surface, leaving a real 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% and both parameters (application_id, command_id) are documented in the schema itself. The endpoint template echoes the same two path parameters but adds no format, type, or constraint detail beyond the schema, which is the baseline expectation.

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 is essentially the tool name restated verbatim ('Get Global Application Command') with an HTTP endpoint appended. The endpoint path does hint at retrieving a single command scoped to an application, but no distinguishing language separates it from siblings like get_guild_application_command or list_global_application_commands.

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 guidance on when to use this versus the guild-scoped getter, the list variant, or the permissions getter. The only cue an agent gets is what it can infer from the name itself, which the instructions say not to rely on.

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