Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_config_set_many

Set multiple configuration values at once to apply a group of related settings, such as changing location coordinates, city, and timezone together.

Instructions

Set multiple configuration values at once. Useful when applying a group of related settings, e.g. changing location (latitude + longitude + city + timezone).

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": {
      "settings": "<settings>"
    },
    "name": "kernel_config_set_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYesArray of key-value pairs to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the word 'Set'. For a batch mutation it never says what happens on partial failure, whether the batch is atomic, whether existing unrelated config is preserved, or whether elevated permissions are needed.

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 sentences, both front-loaded: the operation first, then the motivating scenario. Nothing is redundant and the example earns its place by illustrating the grouping case.

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?

The schema is small and fully described, so callers can construct the arguments without help. However, a batch write tool with no annotations and no output schema should at minimum say whether the result reports per-key success or whether the whole call fails, and the description is silent on that.

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 array structure and the key/value item semantics are already documented. The description adds only the location example as evidence of what keys and groupings look like, which is mild value on top of a self-documenting schema; baseline 3 is appropriate.

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 ('Set multiple configuration values') plus the batch scope ('at once'), which implicitly separates it from the single-value sibling kernel_config_set. It does not name that sibling explicitly, so an agent must infer that kernel_config_set handles the one-at-a-time case.

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?

Gives a concrete when-to-use condition — applying a group of related settings — and reinforces it with the location example (latitude + longitude + city + timezone). It omits any when-not guidance, such as preferring kernel_config_set for a single key or kernel_config_get/catalog for inspection.

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