Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_list

List all agent definitions and optionally filter by active status to inspect which autonomous agents are available in the kernl server.

Instructions

List all agent definitions, optionally filtered by active status

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_agents_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNoFilter by active status

Output Schema

NameRequiredDescriptionDefault
totalYes
agentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/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 full behavioral burden. "List all" does convey a read-only, unfiltered-by-default retrieval, but it says nothing about result limits, pagination, permission requirements, or whether inactive/deleted definitions are included by default when the filter is omitted.

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 sentence, front-loaded with the verb and resource, with the optional filter appended. Nothing is wasted and nothing needs reordering.

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?

This is a simple single-optional-parameter list tool with full schema coverage and an output schema, so return values need no explanation. The only real gap is default/pagination behavior when the filter is omitted, which is minor for a tool of this complexity.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter's schema description ("Filter by active status") already fully explains its meaning. The description restates the same filter without adding syntax, default behavior, or the consequence of omitting it, so the baseline of 3 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 agent definitions") plus the filtering scope, so an agent can distinguish this from the many non-agent list siblings by name alone. It stops short of explicitly contrasting with adjacent agent-related tools such as kernel_agents_directory or kernel_agents_env_list.

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 implied by the phrase "optionally filtered by active status", which hints that omitting the filter returns everything. There is no explicit when-to-use guidance, no indication of when a different listing tool (flows, envs, subscriptions) is the right choice, and no exclusions.

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