Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_import

Import a marketplace package from JSON to add agents, flows, themes, or templates into your workspace.

Instructions

Import a marketplace package from JSON. Supports agents, flows, themes, templates.

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": {
      "package_json": "<package_json>"
    },
    "name": "kernel_marketplace_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
package_jsonYesJSON string of the package to import

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. It does not say whether import overwrites or merges existing agents, flows, or themes, whether it validates the JSON, whether it may be destructive, or what happens if the package is malformed. For a mutation tool, those omissions are significant.

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?

Two short sentences with the action front-loaded and no filler. The second sentence usefully enumerates the supported package types, though it leaves other dimensions under-specified.

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 one-parameter mutation tool with no annotations and no output schema, the definition should state side effects and expected response, such as whether items are created or replaced and what identifiers are returned. The description omits both, so an agent cannot predict the outcome of a call.

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?

There is a single parameter, and the schema describes it as "JSON string of the package to import," so coverage is effectively complete. The description adds no format details, schema shape, or example beyond that, so 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 names a specific verb and resource: "Import a marketplace package from JSON." It also lists the supported package contents, so an agent knows what kinds of assets it can import. However, it does not distinguish this tool from siblings such as kernel_marketplace_install or kernel_marketplace_catalog_install, which plausibly also add packages.

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?

The description gives no indication of when to use this tool rather than install, catalog_install, or office_pack_import. It states neither prerequisites, such as needing a previously exported JSON file, nor exclusions. An agent must infer the use case from the name alone.

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