Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_marketplace_get

Fetch detailed information for a marketplace item by slug or ID. Use it to identify and review specific listings.

Instructions

Get detailed information about a marketplace item by slug or ID.

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": {
      "identifier": "<identifier>"
    },
    "name": "kernel_marketplace_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesItem slug or ID

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 burden. 'Get' signals a read-only, non-mutating operation, which is useful, but nothing is said about permissions, scoping, error behavior for unknown identifiers, or rate limits. For a simple read that is a modest gap rather than a critical one.

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 front-loaded sentence with no wasted wording and the lookup key stated up front. It is efficient, though its brevity leaves little structure to front-load beyond the identifier hint.

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 one-parameter read tool with a fully-covered schema and no output schema, the definition covers the essentials. It nonetheless never indicates what 'detailed information' comprises or whether an unknown identifier errors, so an agent cannot fully predict the response.

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% and the single parameter is documented as 'Item slug or ID', matching the description's 'by slug or ID' almost verbatim. The description adds no format examples, casing rules, or fallback behavior beyond the schema, so the baseline of 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 states a specific verb and resource ('Get detailed information about a marketplace item') and names the lookup key ('by slug or ID'). This clearly separates it from browse/catalog-style siblings, though it never explicitly names an alternative to confirm the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: because an identifier is required, the agent can infer this is a follow-up to a browse/search call, but no when-to-use, when-not-to-use, or alternative tool is stated. The phrase 'by slug or ID' is the only signal about when this tool applies.

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