Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_global_application_command

Creates a global Discord application command so you can define its name, description, options, permissions, and localization settings via the API.

Instructions

Create Global Application Command. [POST /applications/{application_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>",
      "name": "<name>"
    },
    "name": "create_global_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
nsfwNoAge-restricted
typeNoType
handlerNohandler
optionsNooptions
contextsNocontexts
descriptionNoDescription
application_idYesApplication (app/bot) ID
integration_typesNointegration types
name_localizationsNo
description_localizationsNo
default_member_permissionsNo

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=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only the endpoint path, saying nothing about required auth scopes, whether global registration is rate-limited or slow to propagate, or that the operation is additive rather than overwriting.

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?

The description is short and front-loaded, but it is under-specified rather than genuinely concise; the bracketed route adds little that an agent can act on.

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

Completeness2/5

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

This is a mutation tool with 12 parameters, several of which use opaque numeric enums, and no output schema. Given that complexity, the description should explain the global-vs-guild distinction, permission requirements, and the encoded fields, and it does none of these.

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

Parameters2/5

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

Schema description coverage is 75% across 12 parameters, and the schema descriptions themselves are minimal one-word labels ('Type', 'handler', 'contexts', 'options'). The tool description adds no clarifying meaning for any parameter, including the numerically encoded 'type', 'handler', 'contexts', and 'integration_types' fields whose semantics are non-obvious.

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 ('Create Global Application Command') and appends the raw HTTP route, which does convey a verb and resource. However, it does not explain what an application command is or how a global command differs from the sibling create_guild_application_command, so differentiation is left entirely to 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 guidance on when to use this tool versus the guild-scoped variant, no prerequisites, and no mention of required bot permissions or the propagation delay typical of global command registration. The agent must infer the choice between global and guild commands from the tool names alone.

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