From 9813732e5fe63d89a228205496f51953f9b97edc Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 6 Nov 2026 00:52:35 +0200 Subject: [PATCH] fix(giellie): say what "applied" means on a dry run On a dry run nothing is written, so a row the engine reports as applied only means it would be applied. The tool description said none of that, and a reader of the description alone still got the old ambiguity. --- src/app/api/mcp/route.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/app/api/mcp/route.ts b/src/app/api/mcp/route.ts index 00c824e..739ce86 100644 --- a/src/app/api/mcp/route.ts +++ b/src/app/api/mcp/route.ts @@ -2211,7 +2211,7 @@ const tools = [ 'Use mode "set" when the number is the new quantity on hand (the stocktake case), and mode "add" when it is a change to add to the current quantity. ' + "Each line is resolved by exact SKU first, then by a description match (flagged as such). A line that cannot be resolved is reported, never guessed. " + "Quantities are truncated to whole units. One SKU may appear only once in a batch — a repeated SKU rejects the whole batch, so split the paste. " + - "Pass dry_run true first to preview the before/after plan. Quantities may be negative — the till oversells on purpose and the stocktake corrects it. " + + "Pass dry_run true first to preview the before/after plan; on a dry run a row reported as applied only means would be applied, because nothing is written. Quantities may be negative — the till oversells on purpose and the stocktake corrects it. " + "Writes a stock_ledger row against the acting user and mirrors the new quantity onto the price-list catalogue.", inputSchema: { type: "object",