Skip to main content
Glama
Sign In
kconfig-mcp

kconfig-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kconfig_unload

Unload a previously loaded Kconfig session by name so its symbols and configuration state no longer affect later reasoning or queries.

Instructions

Forget a loaded session.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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 for what is apparently a state-removing operation. "Forget" weakly hints at discarding state but nothing is said about whether unsaved changes are lost, whether the session must exist, or what happens on an unknown name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short and front-loaded with no filler, so it is concise. However, that brevity comes at the cost of under-specification rather than efficiency, leaving the reader with almost nothing actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 need not be explained, but for a session-mutating tool with no annotations and an undocumented required parameter the description is far too thin. Critical context about state loss and identification of the session is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `name` has 0% schema description coverage, and the description never mentions it at all. The word "session" only hints that `name` identifies the loaded session, which is far short of compensating for the undocumented schema.

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

Purpose2/5

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

"Forget a loaded session" only restates the tool name with a loose synonym; "forget" is not a concrete verb and it never says the session is unloaded/discarded or what state that touches. It gives no basis for distinguishing this from siblings such as kconfig_load or kconfig_sessions beyond an inverted guess.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no precondition (e.g. the session must currently be loaded), and no mention of an alternative path. The agent must infer entirely from the name that this is the inverse of kconfig_load.

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