Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_browse

Browse marketplace items including extensions, agents, flows, themes, and templates, and filter by type, category, or search query to locate resources for your needs.

Instructions

Browse the marketplace: list extensions, agents, flows, themes, and templates. Filter by type, category, or search query.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort order (default: featured first, then newest)
typeNoFilter by item type
queryNoSearch by name/description/tags
categoryNoFilter by category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; 'Browse... list' does convey a read-only, non-mutating operation, which is the key behavior an agent needs to know. It says nothing about pagination, result caps, or ordering beyond what the schema's sort parameter already documents, so it is adequate but thin for an annotation-free tool.

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?

Two short sentences, zero filler, with the core action and the item types front-loaded before the filtering options. Nothing is repeated or wasted.

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 simple optional-parameter listing tool whose schema is fully documented, the description covers what is listed and how to filter it. Since no output schema exists, it could have said something about the shape or pagination of results, which is the only notable omission.

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%, with all four parameters (including two enums) fully documented in the schema itself, so the baseline is 3. The description restates type, category, and query but adds no syntax or format detail, and omits mention of the sort parameter entirely.

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 pairs a specific verb ('Browse... list') with the resource (the marketplace) and enumerates the five item types returned (extensions, agents, flows, themes, templates). It does not, however, distinguish itself from near-identical siblings such as kernel_marketplace_catalog_browse or kernel_store_browse, so an agent cannot tell from the description alone which of these listing tools to pick.

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 states which filters are available but never says when to use this tool versus the catalog or store browse siblings, nor any prerequisite or exclusion. Given at least two sibling tools with apparently overlapping browse behavior, the absence of any routing guidance is a meaningful gap.

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