Open Kioku

Overview Schema Source Related Servers Discussions Admin

Open Kioku Propose Patch

propose_patch

Read-onlyIdempotent

Draft a patch plan with file edits and context bounds before modifying code. This read-only action helps you outline changes safely, enabling review and approval prior to applying edits.

Instructions

Propose a patch plan (file edits, context bounds) for a task. Read-only; does not write any files. Use to draft a patch plan without modifying files. Prefer plan_change for evidence-backed planning and apply_patch only after explicit approval in write-enabled mode. This is read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task`	Yes	A natural language description of the changes to propose.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`value`	No	Wrapped non-object output, used for Markdown, TOON, or scalar responses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.3Jul 4, 2026

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"
+}

Changed1 schema field changedv2.0.3Jun 10, 2026

changedInput schema / properties / task / description

Previous value: -"Natural language description of the change"New value: +"A natural language description of the changes to propose."

First observedv2.0.1Jun 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Description reinforces annotations (readOnlyHint=true, destructiveHint=false) by stating 'Read-only; does not write any files.' Adds no new behavioral nuance beyond annotations, but is consistent and clear.

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?

Three concise sentences with no wasted words. Front-loaded with purpose and key constraint (read-only). Usage guidance follows naturally.

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?

With one parameter and output schema present, description adequately covers purpose and usage. Could optionally mention output structure but not required given output schema.

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 documentation covers 100% of the single parameter (task). Description does not add additional meaning beyond the schema's description.

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?

Explicitly states verb 'propose' and resource 'patch plan' with clarification that it is read-only and does not write files. Clearly distinguishable from siblings like plan_change (evidence-backed) and apply_patch (write).

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?

Provides explicit when-to-use (drafting patch plan without modifying files) and when-not-to-use (prefer plan_change for evidence, apply_patch only after approval in write mode). Names specific alternatives.

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