Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Plan server build

plan_server_build
Read-only

Validate a blueprint against the live server and stage an ordered build plan. Checks Discord limits, name collisions, role references, feature requirements, and the bot's permissions, and reports every problem at once. Changes nothing.

Instructions

Validate a blueprint against the live server and stage an ordered build plan. Checks Discord limits, name collisions, role references, feature requirements, and the bot's permissions, and reports every problem at once. Changes nothing. Compose the blueprint from the user's request, optionally starting from a reference layout. Existing channels and roles with matching names are reused, never duplicated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
blueprintYesThe desired structure: roles, categories, channels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.0
    • changedInput schema / properties / blueprint / properties / channels / maxItems
      Previous value: -100New value: +500
    • addedInput schema / properties / blueprint / properties / roles / description
      Added value: +"Highest role first, the way the server settings list them. A build creates them in this order and that order is the hierarchy."
    • changedInput schema / properties / blueprint / properties / roles / maxItems
      Previous value: -50New value: +250
  2. Changed9 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / blueprint / additionalProperties
      Removed value: -false
    • removedInput schema / properties / blueprint / properties / categories / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / blueprint / properties / categories / items / properties / channels / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / blueprint / properties / channels / items / $ref
      Removed value: -"#/properties/blueprint/properties/categories/items/properties/channels/items"
    • addedInput schema / properties / blueprint / properties / channels / items / properties
      Added value: +{
+  "name": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "nsfw": {
+    "type": "boolean"
+  },
+  "posting_roles": {
+    "description": "With read_only: role names that may still post.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "private_to": {
+    "description": "Role names that can see this channel. Everyone else is denied view.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "read_only": {
+    "description": "Deny sending for everyone; for rules and announcements.",
+    "type": "boolean"
+  },
+  "slowmode_seconds": {
+    "maximum": 21600,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "topic": {
+    "maxLength": 1024,
+    "type": "string"
+  },
+  "type": {
+    "description": "Default text.",
+    "enum": [
+      "text",
+      "voice",
+      "forum",
+      "stage",
+      "announcement"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / blueprint / properties / channels / items / required
      Added value: +[
+  "name"
+]
    • addedInput schema / properties / blueprint / properties / channels / items / type
      Added value: +"object"
    • removedInput schema / properties / blueprint / properties / roles / items / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it with 'Changes nothing.' It then adds substantive behavior beyond the annotation: the specific check categories (limits, collisions, role references, feature requirements, bot permissions), batch error reporting, and the reuse-never-duplicate rule for matching names. This is exactly the extra context a planner needs.

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?

Five short sentences, front-loaded with the core action and validation scope; the reuse rule and no-mutation guarantee follow in order of importance. No filler.

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?

With no output schema, the description still conveys that it returns a staged, ordered plan plus an all-at-once problem report, which is enough for invocation. It stops short of describing the shape of the returned plan, a minor gap given the read-only nature.

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: names in the blueprint resolve against existing entities and are reused rather than duplicated, and the blueprint should be composed from the user's request. That directly informs how to populate the blueprint parameter.

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 specific verbs (validate, stage) and resources (blueprint, build plan), and the scope is unmistakably distinct from execute_build_plan, diff_blueprint, and save_blueprint. An agent can select it without opening the schema.

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?

Sets the pre-execution context clearly and points at a reference layout as an optional starting point, which routes to get_reference_layout. It never explicitly names execute_build_plan as the follow-on step or states when not to use this tool, so it falls short of full when/when-not 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