Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Register app command

register_app_command

Register a slash command, or update it in place if the name is already taken. Pass a guild while iterating: guild commands appear immediately, while global commands can take up to an hour to show up everywhere and are rate limited per day.

Instructions

Register a slash command, or update it in place if the name is already taken. Pass a guild while iterating: guild commands appear immediately, while global commands can take up to an hour to show up everywhere and are rate limited per day. Subcommands and subcommand groups are not supported here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot.
nameYesCommand name without the slash, lowercase, no spaces.
guildNoGuild (server) name or ID. Omit to use the default guild.
optionsNoArguments the command takes.
descriptionYesShown to users in the command picker.

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/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds critical behavioral context: upsert semantics (update in place if name exists), propagation delay for global commands (up to an hour), rate limits per day for global commands, and explicit exclusion of subcommands. Missing: permission requirements and whether this overwrites existing options.

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: core action, guild propagation nuance, and scope exclusion. Front-loaded with the main verb and upsert behavior. No redundancy against structured fields.

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?

Given no output schema and full schema coverage, the description is complete for correct invocation: it covers core action, upsert behavior, guild propagation nuance, rate limits, and scope exclusions. An agent has enough to decide when and how to call it.

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 schema fully documents all 5 parameters. The description adds semantic value beyond the schema by explaining the practical effect of the guild parameter (immediate vs delayed, rate limits) and the name behavior (upsert). For a tool with complete schema coverage, this is above baseline.

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+resource ('Register a slash command') and adds crucial scope detail: upsert semantics ('or update it in place if the name is already taken') and exclusions ('Subcommands and subcommand groups are not supported here'). Sibling tools register_app_command, update_app_command, and list_app_commands are clearly differentiated by verb.

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

Usage Guidelines4/5

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

Explains when to pass a guild: 'guild commands appear immediately, while global commands can take up to an hour to show up everywhere.' This tells the developer how to choose between guild vs global registration. However, it does not explicitly name when to use register_app_command vs update_app_command (for existing commands with a different name).

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