Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_chain

Create a declarative chain between two agents so the source's completion automatically triggers the target, with optional result passing, delays, and conditions.

Instructions

Create a declarative chain between two agents. When the source agent completes, the target agent is automatically triggered.

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": {
      "source_agent_id": "<source_agent_id>",
      "target_agent_id": "<target_agent_id>"
    },
    "name": "kernel_agents_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoLabel for this chain connection
delay_msNoDelay in ms before triggering target (default: 0)
conditionNoJSON condition: {"status":"completed"}, {"result_contains":"keyword"}, {} = always
pass_resultNoPass source result as context to target (default: true)
source_agent_idYesSource agent ID (triggers the chain on completion)
target_agent_idYesTarget agent ID (receives the chain)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavior burden. It does disclose the core behavioral trait — the target fires automatically when the source completes — but says nothing about whether the chain is validated (duplicate chains, cycles), whether creation is idempotent, what is returned, or what happens if the source agent does not exist.

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 tight sentences with the operation front-loaded and the mechanism immediately after; nothing is redundant or padded.

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 tool with no annotations and no output schema, the description covers purpose and triggering semantics but omits return value, failure conditions, and relationship to other chaining/trigger tools. Adequate to attempt a call, but not complete for correct selection.

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%, and the schema already documents label, delay_ms, condition, pass_result, and both agent IDs with defaults. The description adds no syntax, format, or interaction detail (e.g. how condition interacts with delay_ms), so it sits at the baseline where 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?

States a specific verb and resource ("Create a declarative chain between two agents") and adds the causal semantics in the second sentence. It is clearly a write/binding operation, but it does not name or contrast itself with a near-sibling such as kernel_agents_add_trigger or kernel_agents_flows_create, so sibling differentiation is left to inference.

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?

The trigger-on-completion clause implies the use case (wire agent A's completion to agent B), but there is no explicit when-to-use/when-not guidance, no prerequisites, and no mention of how this differs from add_trigger or flows_create, which the agent must choose between.

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