import { z } from "zod"; import type { McpTool } from "../tool.js"; declare const inputSchema: z.ZodEffects; /** * Backend-assigned uuid of the chunk. Returned by kb_search as the * `id` field on each result row. Use when sourceId isn't known. * Exactly one of sourceId / id must be provided. */ id: z.ZodOptional; }, "strip", z.ZodTypeAny, { id?: string | undefined; sourceId?: string | undefined; }, { id?: string | undefined; sourceId?: string | undefined; }>, { id?: string | undefined; sourceId?: string | undefined; }, { id?: string | undefined; sourceId?: string | undefined; }>; interface Output { /** True when the underlying delete call succeeded (even if 0 rows). */ ok: boolean; /** Number of chunks removed. 0 = nothing matched, treated as success. */ deleted: number; /** Reason when ok=false (e.g. engram doesn't expose delete on this release). */ reason?: string; } /** * Remove a chunk from the knowledge base. * * Round-trips to engram's memory_delete via the optional `delete()` * method on EngramAccess. Older engram releases that don't expose * delete return ok:false with a clear reason — the renderer should * surface this as "your engram backend is too old" rather than * pretending the delete worked. * * The Pyre Knowledge card uses this for the per-result delete affordance * in the search results pane: search → find an unwanted chunk → * one-click remove → re-search to confirm. */ export declare const kbDelete: McpTool; export {}; //# sourceMappingURL=kb-delete.d.ts.map