Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_config_list

List kernel configuration settings, optionally filtered by category, with sensitive API keys and tokens automatically masked for safe inspection.

Instructions

List all kernel configuration settings, optionally filtered by category. Sensitive values (API keys, tokens) are automatically masked.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category: general | ai | chat | agents | notifications | integrations | life | security | advanced

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful, non-obvious behavior: sensitive values such as API keys and tokens are masked in the output. However, it says nothing about ordering, pagination/result size limits, or whether any authentication or permission scope is required.

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 with zero waste: purpose and filter scope first, then the security-relevant masking note. Nothing is padded or redundant.

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 read-only listing tool with one optional enum parameter and no output schema, the description covers purpose, filterability, and output sensitivity handling. The remaining gap is behavioral detail on result size/ordering, which is minor at this complexity.

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% and the single parameter is a documented enum, so the schema already does the work. The description only restates that category filtering exists, adding no meaning beyond the schema's enumerated values.

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?

States a specific verb and resource ("List all kernel configuration settings") plus the optional filter dimension. An agent can tell it reads the full config set rather than a single entry, though it never explicitly contrasts itself with kernel_config_get or kernel_config_catalog.

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?

The phrase "optionally filtered by category" implies when the filter is worth using, but there is no explicit guidance on when to call this versus kernel_config_get (single setting) or kernel_config_catalog. Usage is inferable from the name and wording rather than stated.

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