Skip to main content
Glama

edit_session_decision

Edit or delete a decision in the current session before it is synced, allowing you to curate decision history prior to commit.

Instructions

Edit or delete a decision in the current session.

Use this when reviewing decisions before commit:

  • action: "update" - Modify the decision fields

  • action: "delete" - Remove the decision entirely

Only ephemeral (in-flight) session decisions are editable. Once a decision is synced to Kawa Code, it is immutable — refine it instead by recording a new decision with supersedes: [<id>].

This allows users to curate their decision history before it's persisted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: update modifies the decision, delete removes it
updatesNoPartial fields to update (only for action=update)
intentIdYesThe intent ID the decision belongs to
repoPathYesLocal path to the repository root
decisionIdYesThe decision ID to edit or delete
forkAuthorNoFork attribution; usually resolved by Muninn automatically — pass only for override / testing.
repoOriginNoGit remote origin URL. Auto-detected from repoPath via git if not provided.
workspaceIdNoWorkspace identifier; usually resolved by Muninn automatically — pass only for override / testing.
Behavior4/5

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

Discloses that only ephemeral session decisions are editable and that synced decisions are immutable. Notes that forkAuthor and workspaceId are auto-resolved. Could add more on side effects or reversibility, but given no annotations, it's strong.

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?

Very concise: a one-line summary, bulleted actions, a constraint sentence, and a purpose sentence. No wasted words, well organized.

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 mutation tool with no output schema, the description adequately covers purpose, usage constraints, and parameter context. Slightly incomplete in not describing return values, but overall sufficient for correct invocation.

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 baseline is 3. Description adds value by noting auto-resolution for forkAuthor and workspaceId and clarifying actions, but doesn't elaborate on updates fields beyond schema.

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 clearly states 'Edit or delete a decision in the current session.' It distinguishes from sibling tools like record_decision (create) and get_session_decisions (read) by specifying this is for reviewing before commit.

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 when to use ('when reviewing decisions before commit'), provides the two actions (update/delete), and explicitly warns that synced decisions are immutable, directing to use record_decision with supersedes instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kawacode-ai/kawa.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server