Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_env_report

Report environment blockers such as a down DEV system, missing credential, or broken deploy using a stable key. Join an existing report or park work until it is fixed.

Instructions

Report that something in your office's environment blocks your work (DEV down, a missing credential, a broken deploy). Use the same short key every time for the same problem (dev-e2e, credential-dev-patient-jwt). If it is already open you just join it — nobody is asked again. You get a letter when it is fixed: park the work until then.

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": {
      "key": "<key>"
    },
    "name": "kernel_agents_env_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesShort stable key of the problem, e.g. `dev-e2e`.
subjectNoWhat you parked because of it, e.g. `web#2653:a-b`.
descriptionNoWhat is broken, as you saw it (first reporter's text is kept).
__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.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses idempotency ("if it is already open you just join it — nobody is asked again"), that the first reporter's text is retained, and that a notification arrives on resolution. It omits who can see the report and what the call returns immediately.

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?

Three tight sentences, front-loaded with the action and followed by the key convention and the expected consequence. "You get a letter when it is fixed" is slightly metaphorical but compact and informative; no filler.

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?

No annotations and no output schema exist, so the description is the only source of behavioral detail, and it covers lifecycle and idempotency well. It does not say what a call returns (a report identifier? the joined report?) or how the caller's agent identity is attached, which matters for a four-parameter tool.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real semantics beyond the schema: the key must be short, stable and reused across reports of the same problem, with illustrative values (`dev-e2e`, `credential-dev-patient-jwt`). That convention is not derivable from the schema's field descriptions alone.

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 — "Report that something in your office's environment blocks your work" — and enumerates concrete examples (DEV down, missing credential, broken deploy). It never names the adjacent tools (kernel_agents_env_list, kernel_agents_env_resolve), so an agent must infer that reporting differs from listing or resolving, but the core action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the trigger condition: use this when the environment blocks your work, and it tells you what to do afterward ("park the work until then"). It also prescribes a usage convention — reuse the same short key per problem — which is genuine when/how guidance. It stops short of naming alternatives for looking up or closing existing reports.

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