Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_theme

Activate, deactivate, or preview a marketplace theme to control its live status and appearance before applying changes.

Instructions

Manage themes: activate, deactivate, or preview a theme.

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": {
      "action": "<action>"
    },
    "name": "kernel_marketplace_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesTheme action
item_idNoTheme item ID (required for activate/preview)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and does not meet it. It does not say whether activate/deactivate are idempotent, whether deactivate requires the item_id, whether preview mutates any state or is a safe read, or what permissions are needed.

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, front-loaded with the resource and then the operations; no wasted words. The leading "Manage themes" is mildly redundant with the actions that follow but costs little.

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 tool with a full enum and no output schema, the definition is minimally adequate. It omits the state effects of each action and the deactivate/idempotency behavior that an agent would need to call it confidently.

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% and the schema already documents the action enum and that item_id is required for activate/preview, so baseline is 3. The description adds no format, default, or conditional detail beyond the schema.

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 names the specific resource (themes) and enumerates the three concrete operations: activate, deactivate, preview. That is enough to tell it apart from sibling install/uninstall/browse tools, even though no sibling is named explicitly.

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?

It lists what the tool can do but gives no guidance on when to pick each action versus alternatives such as kernel_marketplace_install, nor whether a theme must already be installed before activating or previewing it. The agent must infer all prerequisites and selection logic.

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