Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

install

Add a rule, skill, workflow, or agent to your project so future AI sessions load it automatically; supports opencode, Claude Code, Cline, and Codex.

Instructions

Install a content item (rule, skill, workflow, or agent) into the current project so it is loaded automatically in future sessions. Supports opencode, Claude Code, Cline, and Codex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath of the content to install (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.

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 agent. 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 and does disclose the key persistence trait (loaded automatically in future sessions). However it omits that this writes/modifies project config, what happens on conflicts, and the gating behavior referenced by the force parameter.

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?

Two sentences, front-loaded with the action and target, no filler. The second sentence earns only partial keep since it partly restates the schema enum while omitting one value.

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?

There is no output schema, so the description should ideally explain what install produces (files/config touched) and clarify gating, which it does not. For a mutation tool with no annotations, the explanation of side effects and preconditions is thinner than ideal.

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%, so the schema documents all five parameters, making 3 the baseline. The description adds no parameter detail and in fact lists only four supported agents (opencode, Claude Code, Cline, Codex), omitting 'copilot' from the enum, which slightly under-informs.

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 (install) and resource (content item: rule, skill, workflow, or agent) plus the effect (auto-loaded in future sessions). It does not explicitly differentiate from close siblings like reinstall, update, or write, so it stops short of a 5.

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?

Gives implied context ('into the current project so it is loaded automatically in future sessions') but never says when to use install versus reinstall, update, or write, nor any exclusions or prerequisites. Usage is inferable rather than stated.

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