Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_extensions_install_bundle

Install an extension from a local .kernl bundle path to add packaged functionality to the kernl MCP server.

Instructions

Install an extension from a local .kernl bundle path.

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": {
      "bundle_path": "<bundle_path>"
    },
    "name": "kernel_extensions_install_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does almost nothing with it. It does not say whether an existing install is overwritten, whether the extension is activated after install, what permissions or trust checks apply, or how failures (bad bundle, version conflict) are surfaced.

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?

A single short sentence with the key qualifier front-loaded and no filler. It is efficiently sized, though the terseness leaves no room for the behavioral context a mutation tool needs.

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

Completeness2/5

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

For a mutation tool with zero annotations, no output schema, and no parameter descriptions, the definition is under-specified. An agent cannot tell what a successful install produces, whether it is idempotent, or what side effects to expect beyond placing files.

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 0% for the single bundle_path string, but the description partially compensates by specifying that it is a local filesystem path to a .kernl bundle file, which implies a format and rules out URLs or marketplace IDs. It still omits path conventions, whether relative paths are accepted, and whether the file must be uncompressed.

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 (extension) plus the source qualifier 'local .kernl bundle path', which distinguishes it from the marketplace/store install siblings that presumably fetch remotely. It does not name a sibling explicitly, so it stops short of the top tier.

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 phrase 'from a local .kernl bundle path' implies this is the choice when you already have a bundle on disk rather than pulling from a marketplace or store, but there is no explicit when-to-use or when-not-to-use statement and no prerequisites are mentioned.

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