Skip to main content
Glama

pre_edit_acknowledge

Mark decision IDs as consciously overridden, preventing re-firing of pre-edit checks for the session.

Instructions

Mark decisions as consciously overridden for the rest of this session.

Phase 3's PreToolUse hook calls this when the agent passes force: true on an Edit tool call to bypass a pre_edit_decision_check block. Adds the surfaced decision IDs to an in-memory session cache; subsequent pre_edit_decision_check fires filter those IDs out so the same block doesn't re-fire.

The cache resets when the MCP server process exits (= the agent session ends). For persistent override across sessions, record a fork decision via record_decision(type: "fork", supersedes: [<id>]) instead.

Returns:

  • acknowledged: number of newly-added IDs (existing IDs are deduped silently)

  • cacheSize: total IDs currently in the session override cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoPathNoLocal path to the repository root. Enables repo attribution of the acted-on value-metric.
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. Used only to attribute the acted-on value-metric to a repo.
decisionIdsYesDecision IDs to acknowledge (mark as overridden for the rest of this session)
workspaceIdNoWorkspace identifier; usually resolved by Muninn automatically — pass only for override / testing.
sessionTokenNoSession scope for the force-override cache. Should match the sessionToken passed to pre_edit_decision_check. Defaults to the MCP server's SESSION_ID.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses in-memory cache, reset on server exit, silent dedup, and return values (acknowledged count, cacheSize). Could mention error cases or side effects more explicitly.

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?

Description is front-loaded with purpose, then usage, then behavior, then returns. Some redundancy (e.g., 'the rest of this session' appears twice), but overall each section serves a purpose. Could be slightly shortened.

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 no output schema, description explains return values. Covers lifecycle, dedup behavior, and session scoping. Missing details on error handling (e.g., invalid decision IDs) and if there are any side effects.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds context: repoPath enables repo attribution, forkAuthor and workspaceId auto-resolved, sessionToken defaults to SESSION_ID. This adds value beyond the 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 the tool's purpose: 'Mark decisions as consciously overridden for the rest of this session.' It specifies the context (Phase 3 PreToolUse hook) and differentiates from sibling tools like pre_edit_decision_check and record_decision.

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 says when to use: 'when the agent passes force: true on an Edit tool call to bypass a pre_edit_decision_check block.' Also provides an alternative: 'For persistent override across sessions, record a fork decision via record_decision(type: "fork", supersedes: [<id>]) 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