Skip to main content
Glama

kernel-list_providers

Lists all SPI providers registered with the running kernel and shows each provider's driver origin, including community or enterprise priority.

Instructions

List all SPI providers registered with the running kernel, including driver origin (community/enterprise priority).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'List' implies a non-mutating read, and the mention of driver origin discloses part of what comes back, but there is no statement about ordering, completeness, permissions, or whether the call touches the live kernel. Enough to be viable, not rich.

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?

One front-loaded sentence identifying the resource and the notable returned attribute, with no filler or redundant restatement of the name.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should indicate what is returned; it does so at a high level (providers plus driver origin). The tool is simple and parameterless, so little more is required, though the shape of a provider entry is left unspecified.

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 (100% schema coverage), so there is nothing for the description to disambiguate. Baseline for a parameterless tool 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 and resource: 'List all SPI providers registered with the running kernel.' It also names the extra data returned (driver origin / community vs enterprise priority). It is clearly distinguishable from describe-style siblings such as kernel-describe_subsystem, though it never explicitly contrasts itself with them.

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 phrase 'registered with the running kernel' implies the context of a live/running-kernel inspection, which is adequate usage framing. There is, however, no explicit when-to-use versus when-to-use-something-else guidance or any stated preconditions.

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