MemKernel

Overview Schema Source Related Servers Discussions Admin

memkernel_checkout

Switch this session's active branch to an existing branch, enabling a coding agent to continue work in a different investigation.

Instructions

Switch this session's active branch (it must exist).

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

Input Schema

Name	Required	Description	Default
`branch_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a session-scoped state mutation but does not say what happens on failure, whether uncommitted work is preserved or discarded, whether a lease is required, or whether the switch is reversible.

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?

A single short sentence with the operation front-loaded and the precondition set off in parentheses. Efficient, though the brevity edges into under-specification.

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?

An output schema exists, so return values need not be explained, and the one-parameter surface is simple. Still, for a state-mutating session tool that interacts with fork/rollback/lease siblings, the description omits error behavior and session-scoping details an agent would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema contributes only a name and type. The description adds one useful constraint (branch must already exist), but says nothing about format, source, or how to obtain a valid branch_id.

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 ('Switch') and resource ('this session's active branch'), which clearly separates it from read-oriented siblings like memkernel_list_branches or memkernel_diff_branches. It does not explicitly name a sibling to contrast against, but the effect of the call 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only guidance is the parenthetical precondition 'it must exist'. There is no statement of when to use checkout rather than memkernel_fork_investigation or memkernel_rollback, nor how to discover a valid branch_id (e.g., via memkernel_list_branches).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.