Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update app command

update_app_command

Change a registered Discord command's description or options while leaving unpassed fields intact. Replacing options overwrites the full list, so resend every option to keep.

Instructions

Change a registered command's description or options. Anything not passed is left as it is. Replacing options replaces the whole list, so send every option you want to keep.

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": {
      "command": "<command>"
    },
    "name": "update_app_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it.
guildNoGuild (server) name or ID. Omit to use the default guild.
commandYesCommand name or ID.
optionsNoReplacement option list, replacing the existing one entirely.
descriptionNoNew description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / bot / description
      Previous value: -"Which bot to act as, by name, when more than one is configured. Omit to use the default bot."New value: +"Which bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it."
  2. Changed2 schema fields changedv1.4.0
    • removedInput schema / properties / options / items / properties / choices / items / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / options / items / properties / choices / items / properties / value / type
      Added value: +[
+  "string",
+  "number"
+]
  3. Addedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description must carry the mutation semantics, and it does: it explains partial-update behavior ('Anything not passed is left as it is') and the non-obvious full-replace behavior of the options list. That second point is exactly the kind of surprise an agent needs warned about before calling. It does not cover permissions, rate limits, or failure modes, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each doing distinct work: what it changes, what happens to omitted fields, and the replace-all caveat. The most dangerous behavior is stated last with an imperative 'send every option you want to keep', so nothing is buried or wasted.

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

Completeness5/5

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

For a five-parameter mutation tool with no output schema, this covers the essentials: partial-update semantics, the destructive-by-replacement behavior of the options array, and the target command. The remaining parameters are fully documented in the schema, so no agent-critical information is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the schema describes options as a 'replacement list' while the description spells out the omission rule for every other field and the consequence of sending a partial option list. That is genuine semantic value beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Change a registered command's description or options.' An agent can immediately tell this modifies an existing command rather than creating or removing one. It stops short of naming the sibling tools (register_app_command, delete_app_command) that would sharpen the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'registered command' signals this applies only to commands that already exist, but the description never says when to choose this over register_app_command or delete_app_command, nor what happens if the target command does not exist. Adequate but leaves the routing decision to inference.

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