Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_installed

List AI knowledge items installed in project or global config for supported coding agents, including opencode, Claude Code, Cline, Codex, and Copilot.

Instructions

List all aik-installed content items in the current project config. Supports opencode, Claude Code, Cline, and Codex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYesTarget AI agent (opencode, claude-code, cline, codex, or copilot).
scopeNoScope to list (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": "Scope to list (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

B3.3/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; 'List' implies a safe read, and it discloses the supported agent set. But it says content is in 'the current project config' while the schema allows a global scope, and it does not describe return format, ordering, or behavior for a missing project config.

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 short sentences, front-loaded with the core action and scope, with zero filler.

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 simple read-only list tool with a complete schema, nothing critical is missing, but the global-scope behavior, projectDir fallback semantics, and return shape are left unexplained and there are no annotations or output schema to compensate.

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 all three parameters are already documented in the schema, giving a baseline of 3. The description adds which agents are supported but actually omits 'copilot', which the agent enum includes, so it adds little and is slightly incomplete.

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 and resource ('List all aik-installed content items') with the config location, which is clearer than sibling 'list'. However it does not distinguish itself from the sibling 'list' tool, so an agent cannot tell the two apart from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus the sibling 'list' or 'search'/'get' tools, and no prerequisites stated. It only enumerates supported agents, which is capability info rather than usage direction.

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