Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_config_get

Retrieve the current value of a configuration setting by its environment-variable key, with sensitive values masked.

Instructions

Get the current value of a specific configuration setting by its env-var key (e.g. ANTHROPIC_API_KEY, LIFE_CITY, CHAT_DEFAULT_PROVIDER). Sensitive values are masked.

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": {
      "key": "<key>"
    },
    "name": "kernel_config_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesEnvironment variable name, e.g. ANTHROPIC_API_KEY

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 provided, so the description carries the full behavioral burden. It does disclose one genuinely useful trait – sensitive values are masked – but omits whether unknown keys error out, whether masked values can be distinguished from real ones, and whether the read reflects live or cached state.

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, front-loaded with the action and scope, followed by the one caveat an agent needs. No wasted wording.

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 one-parameter read tool with no output schema, the description covers what it returns (a value), how it is addressed (env-var key), and the one surprising property (masking). Only the tie-in to sibling config tools is missing, which is a minor gap 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%, so the single 'key' parameter is already documented. The description reinforces this by giving example keys (ANTHROPIC_API_KEY, LIFE_CITY, CHAT_DEFAULT_PROVIDER) that show the namespace spans both secrets and config, but adds no format or validation rules. Baseline 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 the current value of a specific configuration setting by its env-var key,' and it even clarifies that the key is an environment-variable name with concrete examples. It implicitly distinguishes itself from the list-style siblings by emphasizing a single specific setting, though it never names those alternatives.

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 implied rather than stated: the reader can infer this is the single-key lookup counterpart to a bulk list, but there is no explicit 'use this when' or 'use kernel_config_list instead when' guidance. No prerequisites or failure conditions are given.

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