Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_tool_search

Search the kernel tool catalog by free-text query to get ranked matches without loading full schemas. Pair with kernel_tool_describe to fetch a tool's schema on demand.

Instructions

Search the kernel tool catalog by free-text query. Returns ranked matches (name + description + tags + score) without dragging their full input schemas into the context. Pair with kernel_tool_describe to fetch one tool's full schema on demand. Replaces the antipattern of dumping every tool into the context window.

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": {
      "query": "<query>"
    },
    "name": "kernel_tool_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesFree-text search query.

Output Schema

NameRequiredDescriptionDefault
totalYes
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose a meaningful behavioral trait: results intentionally omit input schemas to preserve context, and retrieval is ranked. It does not discuss limits, result caps, or pagination behavior, which would matter for an agent deciding how many queries to run.

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?

Front-loaded with the action and scope, then the return shape, then the pairing guidance. The closing sentence about replacing 'dumping every tool into the context window' is slightly rhetorical and partly redundant with the schema-omission point, but it still conveys rationale.

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?

An output schema exists, so return values needn't be spelled out, and the description still sketches them. For a two-parameter search tool this is nearly complete; the only real gap is the unstated semantics of the 'limit' parameter.

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 50%: 'query' is documented in-schema and echoed by the description as free-text, but 'limit' is only given a default with no explanation of its effect. The description adds the notion of ranking but nothing about how limit interacts with result ordering, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the kernel tool catalog') plus the result shape (ranked name + description + tags + score). It also distinguishes itself from the sibling it pairs with, kernel_tool_describe, so an agent can separate the two without opening a schema.

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

Usage Guidelines4/5

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

Explicitly names the companion tool and the condition that selects it ('pair with kernel_tool_describe to fetch one tool's full schema on demand'), which is genuine routing guidance. It stops short of stating when NOT to use this search (e.g., versus domain-specific siblings), so it falls just short of a 5.

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