Skip to main content
Glama

aik_uninstall

Remove an installed content item from your project, deleting the file and config reference. Works with opencode, Claude Code, and Cline.

Instructions

Uninstall a previously installed content item from the current project. Removes the file and the config reference. Supports opencode, Claude Code, and Cline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath of the content to uninstall (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.
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 the file and config reference, but lacks details on irreversibility, permissions, or side effects.

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 sentences: one for purpose and action, one for supported agents. No redundancy, highly efficient.

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?

No output schema and the description gives basic info. However, with sibling tools available, more context about irreversibility or prerequisites would improve completeness.

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% and the description does not add significant meaning beyond the schema. The parameter details in the schema are already clear.

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 action (uninstall), resource (content item), and scope (current project). It distinguishes from siblings like aik_install and aik_delete by specifying removal of file and config reference.

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 it is for previously installed items but does not explicitly state when to use this over aik_delete or aik_uninstall_all. No exclusions or alternative guidance provided.

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