Skip to main content
Glama

kernel-describe_subsystem

Retrieves details for a named kernel subsystem—such as memory, crypto, persistence, or transport—so AI agents can inspect its purpose and behavior.

Instructions

Detail for a single kernel subsystem by name (e.g. memory, crypto, persistence, graph, transport, events, flow, http, security).

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": "kernel-describe_subsystem"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSubsystem name to describe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/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. It implies a read-only lookup but says nothing about what the returned detail contains, whether unknown subsystems error or return empty, or whether the lookup is cheap/cached.

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?

One sentence, front-loaded with the resource and the keying parameter, with no filler. The sentence fragment style is terse but readable; the example list is the only length and it earns its place.

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?

For a one-parameter read tool this is close to adequate, and the name examples cover the biggest unknown. However, with no output schema and no annotations, the description should at least sketch what 'detail' returns; that gap keeps it at minimum-viable-plus.

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 single parameter is fully documented in the schema, which alone would justify a 3. The description goes beyond it by enumerating concrete valid subsystem names (memory, crypto, persistence, graph, transport, events, flow, http, security), effectively supplying an informal enum the schema lacks.

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?

"Detail for a single kernel subsystem by name" names a specific resource (kernel subsystem) and the retrieval action, and the parenthetical example list makes the domain concrete. It does not distinguish itself from near-siblings such as kernel-list_providers or lsp-describe_domain, so it falls short of a 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?

Usage is only implied: the example list signals which names are acceptable, which helps an agent pick a valid argument. There is no explicit statement of when to use this instead of the list/bootstrap tools, nor of what happens with an unknown name.

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