Skip to main content
Glama

aik_reinstall

Reinstall previously installed content by uninstalling the old entry and installing the latest version from the knowledge base. Supports opencode, Claude Code, and Cline.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath of the content to reinstall (e.g. "rules/typescript")
projectDirNoProject directory (defaults to current working directory). Config files are found by walking up.
agentNoTarget AI agent. Auto-detected from existing config files if not specified (opencode, claude-code, cline).
Behavior3/5

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

Without annotations, the description partially bears the burden of behavioral disclosure. It reveals the two-step process (uninstall then install) but omits details about side effects, error handling, or permission requirements.

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?

The description is concise with two sentences that efficiently convey the core action, process, and supported agents without any extraneous information.

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

Completeness4/5

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

The description adequately covers the reinstall process for a tool with 3 parameters and no output schema. It could elaborate on behavior regarding configuration persistence but is otherwise sufficient.

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 already documents parameters. The description adds no additional meaning beyond listing the agents mentioned in the enum, which is already clear from the schema.

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

Purpose5/5

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

The description clearly states the tool's function: reinstalling a previously installed content item by uninstalling the old entry and installing the latest version. It also specifies supported agents, distinguishing it from related tools like install or uninstall.

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 for reinstalling existing items but does not explicitly state when to prefer this over install or uninstall, nor does it provide alternatives or conditions for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openhoat/aik-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server