Omarchy MCP has 46 tools with significant definition gaps. Most tools lack input schemas (only 8 tools have explicit schema definitions visible in source). Descriptions are present but often generic or auto-generated. Tool naming is inconsistent: some follow verb_noun (theme_apply, window_focus) but many are noun_verb (appearance_background_set, network_wifi_connect). Critical security tools (pkg_add, system_power) lack confirmation patterns. Auto-generated tools from omarchy CLI have minimal descriptions. No output schemas documented. Error handling is basic. This is a D-grade server with major structural issues.

• Add explicit input schemas to all 38 tools lacking them. Use Zod or JSON Schema to define parameter types, descriptions, and constraints. Example: theme_current should have schema {} (empty object), theme_list should document limit parameter.
• Expand tool descriptions to 100-200 chars with actionable guidance. Example: 'Get the current theme slug' → 'Returns the active theme identifier. Use this to check the current theme before calling theme_apply() to switch themes. Returns a string slug like "dark-mode" or "light-mode".'
• Add confirmation_request pattern to destructive tools (pkg_add, pkg_remove, system_power, update_system, refresh_config). Include a dry_run parameter or require explicit confirmation before executing irreversible operations.
• Document output schemas for all tools. Specify return type (object, array, string) and field names/types. Example: window_list returns {windows: [{address: string, class: string, title: string, workspace: number}], total: number}.
• Standardize naming to verb_noun convention. Rename appearance_background_set → set_background, network_wifi_connect → connect_wifi, device_brightness → set_brightness. This reduces LLM reasoning overhead and matches production baselines.