Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_export

Exports a marketplace item as a JSON package so you can share it with others.

Instructions

Export a marketplace item as a JSON package for sharing.

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_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem ID to export

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, the description bears the full burden: it does not say whether the JSON package is returned inline or written to a file, whether the item must be installed first, whether permissions are required, or whether any state changes occur. Calling it "export" implies a read, but that is never confirmed, so an agent cannot reason about side effects.

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 twelve-word sentence with the verb-and-resource front-loaded and zero filler. Its brevity is a virtue structurally, though the same leanness is what leaves behavior 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?

There are no annotations and no output schema, so the description is the only source of behavioral information, and it omits what the package contains, how it is delivered, and what happens on an invalid or uninstalled item ID. For an export tool whose result is a file or payload, that leaves the agent guessing.

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 100% with a single required "id" property already documented as "Item ID to export," so the description adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ("Export a marketplace item") plus the output form ("JSON package"), which is far more informative than the bare name. It does not explicitly contrast with nearby siblings such as kernel_marketplace_import or kernel_marketplace_get, leaving the agent to infer the direction of the operation.

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 only hint of usage is the trailing phrase "for sharing," which implies intent but never states when to choose this over kernel_marketplace_get or kernel_marketplace_import. No prerequisites, no exclusions, and no named alternatives are provided.

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