Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Run setup check

run_setup_check
Read-only

Checks Omnicord bot setup health: token validity, gateway intents, guild thresholds, default guild, and npx cache, with fixes for failures. Run first when errors occur.

Instructions

End-to-end health check of the Omnicord setup: token presence and validity, privileged gateway intent toggles, guild count against Discord's verification thresholds, default guild membership, and whether this install runs from npm's temporary npx cache. Every failed check comes with instructions for fixing it. With more than one bot configured, pass bot to check a specific one. Run this first when anything misbehaves.

Input Schema

NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed3 schema fields changedv1.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bot
      Added value: +{
+  "description": "Which bot to act as, by name, when more than one is configured. Omit to use the default bot.",
+  "type": "string"
+}
  3. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the specific checks performed and that each failure returns fix instructions. It stops short of describing return structure/pagination, but for a diagnostic this is rich disclosure.

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

Conciseness4/5

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

Front-loaded with the core purpose, then supporting detail. The sentence about the checks is dense but each clause earns its place; only the npx-cache detail borders on trivia.

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?

Given a read-only single-param diagnostic with annotations covering safety, the description is essentially complete — it covers scope, trigger, remediation, and the multi-bot case. It does not describe the pass/fail output shape, but no output schema exists and this is minor for a diagnostic.

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 coverage is 100% and the sole 'bot' parameter is already documented in the schema. The description restates its usage condition without adding format or syntax detail, so it adds marginal value over structured data — 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+resource ('health check of the Omnicord setup') and enumerates exactly what it verifies: token validity, privileged gateway intents, guild count vs verification thresholds, default guild membership, and npx cache detection. This is clearly distinguishable from every Discord-operation sibling like get_bot_info or list_servers.

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?

Gives a clear trigger ('Run this first when anything misbehaves') and a parameter condition ('With more than one bot configured, pass bot to check a specific one'). No explicit alternatives are named, but there is no true sibling diagnostic tool to contrast against.

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