Skip to main content
Glama
shivyadavus

Open Kioku

by shivyadavus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Open Kioku Plan Change

plan_change
Read-onlyIdempotent

Generate an evidence-backed pre-edit plan for a task, listing primary files, changed-line ranges, expected impact, and test targets. Use it before editing to know what changes affect.

Instructions

Generate an evidence-backed pre-edit plan for a task, including primary files to edit, expected impact, changed-line ranges, and recommended test targets. Use before editing to create an evidence-backed plan with expected files, ranges, impact, and tests. Prefer create_change_contract when the plan must be persisted and verified later. This is read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesA natural language description of the task or change to plan.
limitNoMaximum planning results to generate. Defaults to 20.
sinceNoOptional git revision/range used with git diff --unified=0 to include changed files and line ranges in planning context.
formatNoThe format of the plan.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoWrapped non-object output, used for Markdown, TOON, or scalar responses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The MCP structuredContent object returned by this Open Kioku tool. Most tools expose their JSON fields directly; string or scalar tool outputs are wrapped as {\"value\": ...}.",
+  "properties": {
+    "value": {
+      "description": "Wrapped non-object output, used for Markdown, TOON, or scalar responses."
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional git revision/range used with git diff --unified=0 to include changed files and line ranges in planning context.",
+  "type": "string"
+}
  3. Changed3 schema fields changedv2.0.3
    • changedInput schema / properties / format / description
      Previous value: -"Output format"New value: +"The format of the plan."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum planning results to generate. Defaults to 20."
    • changedInput schema / properties / task / description
      Previous value: -"Natural language task description"New value: +"A natural language description of the task or change to plan."
  4. First observedv2.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds 'This is read-only' and explains the evidence-backed nature, which provides useful context beyond the annotations.

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?

Four sentences, front-loaded with the primary action. Every sentence adds value, with no redundancy or fluff.

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?

Given the tool has an output schema (not shown) and complete parameter documentation, the description adequately covers inputs and output expectations for a planning tool. It mentions the key output components.

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%, so the schema already documents all parameters. The description mentions output components but does not add new semantics for parameters beyond what the schema provides.

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?

The description specifies the verb 'Generate', the resource 'evidence-backed pre-edit plan', and includes specific deliverables: primary files, impact, changed-line ranges, and test targets. It also distinguishes from the sibling 'create_change_contract'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states 'Use before editing' and 'Prefer create_change_contract when the plan must be persisted and verified later', providing clear when-to-use and when-not-to-use guidance with an alternative named.

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