Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_decision_policy_set

Configure how a category of office questions is handled: off, suggest based on past decisions, or auto when precedent precision holds; enable auto only on operator request.

Instructions

Chief only. Set how a kind of question (category) is handled in an office: off, suggest (show what past decisions suggest), or auto (a precedent answers it alone while its measured precision holds). Only turn on auto when the operator asked for it.

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": {
      "flow_id": "<flow_id>",
      "category": "<category>",
      "mode": "<mode>"
    },
    "name": "kernel_agents_decision_policy_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
flow_idYes
categoryYes
min_samplesNo
min_precisionNo
__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.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the authorization restriction (chief only), what a mutation does (changes how a category is handled), and a safety guardrail on 'auto' tied to measured precision holding plus operator consent. It stops short of saying what happens to an existing policy when modes/min thresholds change.

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?

Front-loads the key constraint ('Chief only') and then the purpose and mode semantics in two compact sentences. The parenthetical mode explanations earn their space; nothing is redundant.

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?

For a 6-parameter mutation with no annotations and no output schema, the definition covers the conceptual model and the auto-mode guardrail but leaves min_samples/min_precision unexplained and does not say what is returned on success. Adequate but with clear gaps.

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 only 17% (just the internal caller id), so the description must compensate. It explains the three 'mode' values with meaningful semantics, which is genuinely additive, but says nothing about flow_id, category, min_samples, or min_precision, leaving half the parameters undocumented.

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 (set) and resource (per-category handling of a kind of question in an office), and defines each of the three modes in-line. It is clearly differentiable from kernel_agents_decision_stats (read stats) though it never names a sibling explicitly.

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?

Gives two concrete usage constraints: 'Chief only' (caller must be the chief) and 'Only turn on auto when the operator asked for it'. That is real when-to-use/when-not guidance, but there is no explicit routing to alternative tools for inspecting or reverting policy.

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