Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update app command

update_app_command

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.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot.
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.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"
+]
  2. Addedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the tool is a mutation. The description adds valuable behavioral context: 'Anything not passed is left as it is' clarifies partial update semantics, and 'Replacing options replaces the whole list, so send every option you want to keep' warns about destructive replacement of options. This goes beyond annotations and helps prevent accidental data loss.

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 sentences, each earning its place. The first states purpose, the second clarifies partial update, the third warns about option replacement. Front-loaded and zero waste.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers the key behavioral aspects: partial updates and the all-or-nothing options replacement. It does not mention permissions or bot/guild scoping (though the schema does), but these are less critical for correct invocation. Overall sufficient for an agent to call it correctly.

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%, so the schema fully documents all parameters. The description reiterates the replacement behavior for options, which is already in the schema, and adds no new parameter syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb (Change) and resource (a registered command) and scopes it to description or options. Among the many sibling tools, update_app_command is clearly distinct from delete_app_command, register_app_command, and list_app_commands.

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?

The description implies usage when modifying an existing command, but does not explicitly say when to use this vs register_app_command or delete_app_command, nor does it list any conditions or prerequisites. Adequate but minimal guidance.

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