Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_flows_create

Create a new department/office flow and get its flow ID, then pass that ID to agent creation calls so new agents appear under the correct office in the 3D view.

Instructions

Create a new flow (department / office). Returns the new flow id, which you must pass to subsequent kernel_agents_create calls so the agents show up under this office in the 3D view.

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

Input Schema

NameRequiredDescriptionDefault
nameYesShort office name, e.g. 'Ventas' or 'Content Factory'
colorNoHex color for the 3D room marker, e.g. '#10b981'
descriptionNoOne-line summary of what this office does

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.8/5.0
Behavior3/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 and partially meets it: it discloses that the tool mutates state and that it returns a new flow id, plus the downstream 3D-view consequence. Missing are permission requirements, duplicate-name behavior, validation failure modes, and whether color/description are optional in practice.

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 sentences, zero filler, with the action statement front-loaded ahead of the dependency note. Every clause carries information an agent needs to call and sequence the tool correctly.

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 three-parameter create tool with no output schema, the description covers what it makes and what it returns (the new flow id), which is the key missing piece given the absent output schema. Only mutation-side behavior such as error and permission handling is unaddressed.

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 explains name, hex color, and one-line description with examples, so the description adds no parameter meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 new flow') and immediately resolves terminology ambiguity by equating 'flow' with 'department / office'. It does not differentiate against the similarly named sibling kernel_office_create, which is the one adjacent concept an agent could confuse it with.

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 concrete sequencing guidance: the returned flow id must be passed to subsequent kernel_agents_create calls. That tells the agent this is a prerequisite step rather than a standalone call. It stops short of explicit exclusions (e.g., when to use kernel_office_create instead), so it is clear context without full alternative routing.

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