import { z } from "zod"; import type { McpTool } from "../tool.js"; declare const inputSchema: z.ZodObject<{ /** The id from the corresponding `pending_enrichment_requests` poll. */ id: z.ZodString; /** * The enrichment result. Shape varies by request type — see * `docs/enrichment-protocol.md` for the per-type schemas: * - categorize: `{ category, confidence, tags[] }` * - extract_actions: `{ actions[] }` * - summarize: `{ summary, key_points[] }` * - tag_entities: `{ entities[] }` * Pass `error` instead when the provider couldn't produce a result. */ result: z.ZodOptional; /** Set when the provider couldn't produce a usable result. */ error: z.ZodOptional>; }, "strip", z.ZodTypeAny, { id: string; error?: { code: string; message: string; } | undefined; result?: unknown; }, { id: string; error?: { code: string; message: string; } | undefined; result?: unknown; }>; interface Output { accepted: boolean; /** * "no_queue" → Cortex isn't running in queue mode (has a local LLM). * "unknown_id" → request expired or was never queued. * "ok" → result delivered to the waiting pipeline. */ reason: "ok" | "no_queue" | "unknown_id"; } /** * Counterpart to `pending_enrichment_requests`. Connected MCP * clients post enrichment results back to Cortex with this tool. * Cortex hands the result to the waiting pipeline so ingestion can * proceed with structured metadata. * * Part of Cortex Enrichment Protocol v1. */ export declare const submitEnrichmentResult: McpTool; export {}; //# sourceMappingURL=submit-enrichment-result.d.ts.map