Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

uninstall_all

Remove all aik-installed rules, skills, and workflows from a project or globally, deleting managed files and config references for supported AI agents.

Instructions

Uninstall ALL aik-installed content items from the current project. Removes all aik-managed files and config references.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYesTarget AI agent (opencode, claude-code, cline, codex, or copilot).
scopeNoInstallation scope (project or global).project
projectDirNoProject directory (defaults to current working directory). Config files are found by walking up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "project",
+  "description": "Installation scope (project or global).",
+  "enum": [
+    "project",
+    "global"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changedv0.3.1
    • changedInput schema / properties / agent / description
      Previous value: -"Target AI agent. Auto-detected from existing config files if not specified."New value: +"Target AI agent (opencode, claude-code, cline, codex, or copilot)."
    • changedInput schema / properties / agent / enum
      Previous value: -[
-  "opencode",
-  "claude-code",
-  "cline"
-]New value: +[
+  "opencode",
+  "claude-code",
+  "cline",
+  "codex",
+  "copilot"
+]
    • addedInput schema / required
      Added value: +[
+  "agent"
+]
  3. Addedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that it removes 'all aik-managed files and config references,' which is useful behavioral context. However, it omits irreversibility, permission requirements, and any warning about the destructive nature beyond the word 'Uninstall.'

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?

Two succinct sentences, front-loaded with the primary action and scope. No wasted words; every sentence contributes to understanding.

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

Completeness3/5

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

The description is broadly adequate for a destructive tool, but given no annotations and a scope parameter that allows 'global,' the claim 'from the current project' is potentially incomplete or misleading. It also does not mention the required 'agent' parameter, though the schema covers it.

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 three parameters including enums and default. The description adds no parameter information, which is the baseline 3 when the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb ('Uninstall') and resource ('ALL aik-installed content items') with clear scope ('from the current project'). It distinguishes itself from a singular 'uninstall' sibling via 'ALL', but does not explicitly name alternatives or contrast with the sibling tool.

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 (mass removal) through 'ALL' but offers no explicit when-to-use guidance, no exclusions, and no mention of the sibling 'uninstall' or other alternatives. Adequate but bare minimum.

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