Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_store_update

Run manually to check the store for newer versions of installed, licensed extensions and apply them in place. Never installs new items or runs automatically.

Instructions

Check the Kernl store for newer versions of your installed, licensed extensions and apply them in place. Only touches extensions you've already installed and your license covers — never installs anything new. Free (no license) is a no-op. Manual trigger; nothing runs automatically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does so well: it discloses the mutation scope (installed + licensed only), the safety constraint (never installs anything new), and the no-license no-op case. It omits whether applying updates requires confirmation or whether an agent restart is needed afterward, leaving some operational behavior undisclosed.

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?

Four short sentences, front-loaded with the action, then constraints, then the licensing edge case, then the trigger model. Every sentence carries distinct information and nothing is redundant.

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?

For a zero-parameter tool with an output schema, the description covers what is touched, what is excluded, and when it runs. The remaining gap is post-update behavior (for example, whether a restart is needed), which is relevant given it mutates installed extensions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter meaning to convey and nothing for the description to compensate for. Baseline of 4 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 states a specific verb pair (check for newer versions and apply in place) and a specific resource (installed, licensed extensions in the Kernl store). It implicitly distinguishes itself from kernel_store_install by stating it never installs anything new, but it never addresses how it differs from the closely named sibling kernel_extensions_update.

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

Usage Guidelines4/5

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

The definition establishes clear context: manual trigger, nothing runs automatically, and it applies only to already-installed and licensed extensions. It does not explicitly say when to prefer this over kernel_extensions_update, but the boundary of what it will act on is unambiguous.

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