Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_env_list

List open office environment problems, when each was reported, and who is waiting on it.

Instructions

Read-only. The environment problems open in your office, since when, and who is waiting on each.

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

Input Schema

NameRequiredDescriptionDefault
__caller_agent_idNo[internal] injected by the agent executor when this tool is invoked from an agent run. Not meant to be set by external callers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does supply the safety profile ("Read-only") plus the shape of the returned data (age of each problem, who is blocked). It says nothing about ordering, volume, pagination, or whether the listing is scoped strictly to the caller's office, which are the traits an agent would want before relying on the result.

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?

Two short sentences with the safety constraint front-loaded ahead of the payload description, and no filler. Every clause contributes information the agent needs.

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?

For a simple read-only list with no required parameters and no output schema, the description covers what the tool returns and that it does not mutate state. Minor gaps remain around scope (office-only?) and whether the result set is bounded or paginated.

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 an executor-injected internal field already documented at 100% schema coverage, so there is no caller-facing parameter needing explanation. The description correctly adds nothing here, matching the baseline for a no-required-parameter tool.

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?

Names a specific resource and the exact payload returned: open environment problems in your office, when each started, and who is waiting on each. The verb is only implied by "Read-only" rather than stated, and there is no explicit differentiation from the sibling kernel_agents_env_report or kernel_agents_env_resolve, so it stops 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: an agent can infer this is the way to see currently open problems, and "Read-only" signals it is non-mutating. There is no explicit when-to-use versus kernel_agents_env_report (reporting) or kernel_agents_env_resolve (closing), and no statement about whether resolved problems are excluded.

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