Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_questions_answer

Answer a triage question by selecting one option or writing free text so the asking agent can resume, and flag any operator follow-up to escalate.

Instructions

Chief only. Answer a question in triage: pick one of its options by 0-based selected_index, or write text when none fits. The asking agent gets the answer and resumes.

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": {
      "question_id": "<question_id>",
      "leaves_work_to_operator": "<leaves_work_to_operator>"
    },
    "name": "kernel_agents_questions_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoFree-text answer, when no option fits.
question_idYes
selected_indexNo0-based index of the chosen option (0-3).
__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.
leaves_work_to_operatorYestrue when your answer leaves anything to the operator (they must act, decide, or you are holding until they say so). Then the question is escalated instead of closed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description still discloses the key behavioral facts an agent needs: a role restriction ('Chief only') and the downstream effect ('The asking agent gets the answer and resumes'), which tells the caller this unblocks another agent's run. It does not say whether answers are final/irrevocable or what happens on an out-of-range index.

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?

Three short sentences, front-loaded with the audience restriction, then the action, then the consequence. No filler and nothing an agent must skip past to find the operative instruction.

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 5-parameter action tool with 80% schema coverage and no output schema, the description covers actor, action, mode selection, and the resumption effect. Minor gaps remain around error handling and the finality of an answer.

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 already 80%, so most parameters are self-documenting; the description still adds exclusivity semantics not stated in the schema — choose an option OR supply text when none option fits — which is the crucial decision rule for `selected_index` versus `text`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Answer a question in triage'), names the two answer modes (option index vs free text), and constrains the actor ('Chief only'), which separates it from the triage/escalate siblings without needing their schemas.

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 clear context for use ('in triage', chief-only) and a conditional alternative ('write `text` when none fits'), plus the escalation branch via `leaves_work_to_operator`. It stops short of explicitly naming where an agent should go instead when the question is not theirs to answer.

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