Skip to main content
Glama
Sign In
kconfig-mcp

kconfig-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kconfig_sessions

Lists loaded Kconfig analysis sessions so you can see active session state and resume work on the right configuration tree.

Instructions

List loaded sessions.

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": "kconfig_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation but this is never stated, and there is no mention of ordering, scope (global vs per-workspace), whether unloaded sessions appear, or any side effects.

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?

Three words, front-loaded, with no filler or redundancy. It is arguably too terse rather than verbose, but there is no structural problem or wasted wording.

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 described. But with no annotations and no explanation of what a 'session' is in this Kconfig toolset, the definition leaves an agent guessing about scope, lifecycle, and how the result connects to kconfig_load/kconfig_unload.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline of 4 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?

States a specific verb ('List') and resource ('loaded sessions'), so the operation is identifiable. However, it does not differentiate from siblings like kconfig_load or kconfig_unload by explaining what a 'session' is or how loaded sessions relate to those operations.

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?

No when-to-use guidance and no mention of alternatives. An agent must infer that this is a discovery/enumeration call and that it might precede kconfig_unload or kconfig_diff, but nothing in the description says so.

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