Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reinstall

Uninstall a previously installed content item and install its current version from the knowledge base for AI agents such as Claude Code, Cline, Codex, and opencode.

Instructions

Reinstall a previously installed content item. Uninstalls the old entry and installs the latest version from the knowledge base. Supports opencode, Claude Code, Cline, and Codex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath of the content to reinstall (e.g. "rules/typescript")
agentYesTarget AI agent (opencode, claude-code, cline, codex, or copilot).
forceNoInstall even when gating fails (applies-to/requires). Use only with a documented reason.
scopeNoInstallation scope (project or global). Requires explicit agent for global scope.project
projectDirNoProject directory (defaults to current working directory). Config files are found by walking up./app

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "description": "Install even when gating fails (applies-to/requires). Use only with a documented reason.",
+  "type": "boolean"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "project",
+  "description": "Installation scope (project or global). Requires explicit agent for global scope.",
+  "enum": [
+    "project",
+    "global"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changedv0.3.1
    • changedInput schema / properties / agent / description
      Previous value: -"Target AI. Auto-detected from existing config files if not specified (opencode, claude-code, cline)."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"
+]
    • changedInput schema / required
      Previous value: -[
-  "path"
-]New value: +[
+  "path",
+  "agent"
+]
  3. Addedv0.1.1

TDQS

B3.4/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 usefully discloses the replace-in-place behavior (uninstall then reinstall latest version) and the supported agents, but says nothing about permissions, failure modes, what happens to locally modified files, or the effect of the force/scope gating it references only indirectly.

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?

Three short sentences, front-loaded with the core action and mechanism; little waste. The closing agent list is somewhat redundant with the schema enum but does clarify supported targets.

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?

For a 5-parameter mutating tool with no annotations and no output schema, the description covers the essential action and replacement semantics but leaves gaps around permissions, gating behavior, and result reporting that an agent would want before invoking.

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 already documents path, agent, force, scope, and projectDir in detail; baseline 3 applies. The description adds no parameter syntax or format detail, and its agent list (opencode, Claude Code, Cline, Codex) omits copilot, which appears in the schema enum.

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 (reinstall) plus the resource (previously installed content item) and explains the mechanism: uninstall old entry, install latest version from the knowledge base. This implicitly separates it from install/uninstall siblings, but it never names an alternative explicitly.

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 phrase 'previously installed content item' implies this is for items already present rather than fresh installs, which gives usable context. However, there is no explicit when-to-use vs install/update/check_updates guidance and no stated prerequisites.

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