Skip to main content
Glama

kconfig_what_selects

Trace a Kconfig symbol's select/imply relationships: see who forces or suggests it and what it forces or suggests, with current values and file locations.

Instructions

Who forces this symbol on (select), who suggests it (imply), and what it selects/implies itself - with current values and locations.

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>",
      "symbol": "<symbol>"
    },
    "name": "kconfig_what_selects"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
symbolYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose that results come with current values and locations, but it omits prerequisites (e.g., whether a session or config must be loaded) and error behavior when a symbol does not exist in the current configuration.

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?

A single sentence, front-loaded with the primary question, and the parentheticals efficiently gloss the Kconfig terminology. The trailing 'with current values and locations' clause is useful; nothing is redundant.

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?

An output schema exists, so return values need not be spelled out, and the relationship direction is covered. However, with two required parameters at 0% schema coverage and no annotations, the definition leaves material gaps about argument meaning and preconditions for a two-input query tool.

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?

Schema description coverage is 0% and both parameters are bare strings named 'name' and 'symbol' with no titles beyond the key names. The description refers only to 'this symbol' and never explains what 'name' denotes (presumably the session), leaving an agent to guess where the symbol goes and what the other argument is.

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 names a precise query: inbound 'select' and 'imply' relationships plus the symbol's own outgoing select/imply edges, with current values and locations. That is a specific verb+resource pair an agent can distinguish from a plain symbol lookup or a 'why not' diagnosis. It stops short of naming a sibling for contrast, so it lands at 4 rather than 5.

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 phrasing 'who forces this symbol on' implies the use case of tracing and explaining a symbol's value, but there is no explicit when-to-use, when-not-to-use, or named alternative among kconfig_why_not or kconfig_symbol. Guidance is inferable from the phrasing rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.