Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_application_command

Creates a guild-specific Discord application command for an app, using the application and guild IDs to register slash commands in that server.

Instructions

Create Guild Application Command. [POST /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": "<name>",
      "description": "<description>"
    },
    "name": "create_guild_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
nsfwNoAge-restricted
typeNoType
optionsNo
guild_idYesServer (guild) ID
descriptionYesDescription
application_idYesApplication (app/bot) ID
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 mutation and openness profile is covered. The description adds no behavioral context of its own - no mention of required bot permissions (applications.commands), validation of the command name/description, or immediate registration effects on the guild. The endpoint path is factual metadata, not behavioral disclosure.

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 with the action, so there is no padding. However, brevity here is under-specification rather than economy - the second clause is a route restatement that occupies the only available space without earning it.

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 10 parameters and no output schema, which puts the full explanatory burden on the description; it delivers none of that. An agent would not know what happens on success, whether creation is idempotent with respect to name, or how the command type affects the options payload.

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 only 60% across 10 parameters, and the description supplies no parameter meaning at all. Ambiguous fields such as type (a bare number with no enum), options (untyped array), default_member_permissions, and the localization maps are left for the agent to guess, and nothing in the description compensates.

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 ('Create Guild Application Command') and appends the HTTP route POST /applications/{application_id}/guilds/{guild_id}/commands. The name plus route does convey a concrete verb and resource, but the sentence adds essentially nothing the name did not already say and never distinguishes guild-scoped creation from siblings like create_global_application_command or bulk_modify_guild_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 when-to-use guidance, no prerequisites, and no named alternative. The only implicit signal is the guild_id in the route, which hints that this is the guild-scoped variant, but the agent must infer that from structured data rather than from the description.

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