Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_flows_set_repo

Set the host git repository that an office's agents use as their working directory, or revert to the kernel workspace default. Optionally initialize git in the target path.

Instructions

Promote an office (flow) to a host git repo all its agents work in, or revert it. Pass an absolute path to promote; omit/empty path to revert to the kernel workspace home. Agents without their own cwd_path override will use this directory as cwd.

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

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute host path, e.g. /home/you/projects/my-office. Omit or empty to revert to the kernel workspace.
flow_idYesOffice/flow id (from kernel_agents_flows_list)
git_initNoRun `git init` if the directory is not already a git repo. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key side effect: the chosen directory becomes the cwd for every agent lacking a __cwd_path__ override, so the blast radius of the change is visible. It also frames revert as a distinct mode. Gaps remain on whether promotion moves/copies existing files, what happens if the path is invalid or non-empty, and any permission prerequisites.

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?

Three short sentences with the action and its opposite stated first, then the parameter rule, then the downstream effect. Nearly every clause carries information; only the path semantics overlap with the schema text. Minor jargon ('promote', '__cwd_path__') costs a point.

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 3-parameter mutation tool with no annotations and no output schema, the definition covers purpose, the promote/revert switch, and the effect on agent working directories. It lacks failure-mode and filesystem-side-effect detail, which matters for a tool that relocates where agents execute.

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 100%, so the schema already documents all three parameters, including the omit/empty revert behavior and the git_init default. The description restates the path semantics and adds the cwd consequence, but adds no new format or validation detail beyond what the schema says. Baseline 3 is appropriate.

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 a specific action pair (promote / revert) on a specific resource (an office/flow's working directory), which is far more than a restatement of the name. The parenthetical gloss 'office (flow)' resolves the naming ambiguity. It stops short of explicitly contrasting itself with siblings such as kernel_agents_flows_create, but the verb+resource is unambiguous.

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?

It gives a clear conditional rule for the central decision: pass an absolute path to promote, omit or empty the path to revert to the kernel workspace home. That is explicit when/when-not guidance for the only branchable parameter. It does not name alternative tools for related tasks (e.g. creating a flow), so it is not a 5.

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