Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_decision_stats

Shows decision policies and measured operator alignment by question category, revealing the precision each category needs before past decisions can answer alone.

Instructions

Read-only. Per kind of question (category) in an office: the policy (off / suggest / auto), and how often the operator chose what past decisions suggested — the measured precision a category needs before a precedent may answer it alone.

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

Input Schema

NameRequiredDescriptionDefault
flow_idNoOffice id; defaults to yours.
__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

B3.2/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 behavioral burden. It does disclose 'Read-only', which is genuine safety information, and explains the meaning of the measured precision. However it says nothing about permissions required, whether the result covers all categories or only ones with recorded decisions, or how large/slow the response is.

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 compact sentence front-loads the 'Read-only' qualifier and then specifies the two reported metrics with no filler. The colon-and-em-dash construction is grammatically fragmentary, but every clause 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?

With no output schema, the description reasonably serves as the return-value summary by naming the two fields reported, which is the main thing an agent needs. It omits grouping granularity, whether categories with zero traffic are included, and any notes on interpreting the precision figure, leaving moderate gaps for a statistics tool.

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 description coverage is 100%, so both parameters (flow_id and the internal __caller_agent_id) are already documented in the schema. The phrase 'in an office' loosely maps to flow_id but adds no scoping detail beyond the schema's 'defaults to yours'. Baseline 3 applies when the schema does the work.

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?

The description names the resource precisely (per-category decision policy plus operator agreement rate within an office) and leads with 'Read-only', so an agent can tell this is a reporting tool rather than the mutating sibling kernel_agents_decision_policy_set. The verb is implicit — it enumerates returned fields instead of saying 'returns/reads', which slightly weakens the statement of what the tool does.

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 inspection counterpart to kernel_agents_decision_policy_set, since one reports policy and the other sets it. There is no explicit when-to-use statement, no named alternatives, and no prerequisite or exclusion conditions.

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