Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_catalog_uninstall

Uninstall an installed extension by ID or slug, removing its install directory and installed_extensions record; optionally force removal when other extensions depend on it.

Instructions

Uninstall an installed extension by id or slug. Removes the install dir and the row in installed_extensions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "kernel_marketplace_catalog_uninstall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInstalled extension id or slug
forceNoForce uninstall even when other extensions depend on it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real value by naming the two concrete effects: the install directory and the installed_extensions row are deleted. It stops short of stating irreversibility, what happens to dependent extensions by default, or what errors surface, which matters for a destructive operation.

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 action and selector, followed by the exact side effects. Nothing is redundant or padded.

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 two-parameter destructive tool with no annotations and no output schema, the definition covers the essentials (what is deleted, how to identify the target). It leaves gaps an agent would care about: reversibility, default behaviour with dependents, and what a successful call returns.

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 both `id` (id or slug) and `force` (override dependency blocking) are already fully documented. The description echoes the id-or-slug selection but adds no new meaning: it never explains what happens when `force` is omitted or what form the returned information takes. Baseline 3 applies.

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?

The description uses a specific verb (Uninstall) plus a precise resource (an installed extension) and states the selector (id or slug). It is clear on its own, but it never distinguishes itself from the similarly named siblings kernel_marketplace_uninstall and kernel_extensions_uninstall, so an agent cannot tell them apart from the text 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?

There is no when-to-use guidance, no mention of the alternative uninstall tools, and no stated prerequisites such as needing the extension installed first. The only conditional behaviour (forcing past dependents) is carried by the schema, not the description.

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