import type { DeleteFileInput, IngestDataInput, IngestFileInput, ListFilesInput, QueryDocumentsInput, ReadChunkNeighborsInput, SyncStartInput, SyncStatusInput } from './types.js';
/**
 * Validate `query_documents` arguments. `query` must be a non-empty string;
 * `limit`, when provided, must be a positive integer (the handler defaults it
 * to 10 when absent).
 */
export declare function parseQueryDocumentsInput(raw: unknown): QueryDocumentsInput;
/**
 * Validate `list_files` arguments. The tool historically takes no arguments, so
 * an omitted `arguments` (`undefined`) or `{}` is accepted as "no scope". When
 * `scope` is present, it is normalized the same way as `query_documents`.
 */
export declare function parseListFilesInput(raw: unknown): ListFilesInput;
/**
 * Validate `ingest_data` arguments. `content` must be a non-empty string;
 * `metadata` must be an object with a non-empty `source` string and a `format`
 * in the supported set.
 */
export declare function parseIngestDataInput(raw: unknown): IngestDataInput;
export declare function parseIngestFileInput(raw: unknown): IngestFileInput;
export declare function parseDeleteFileInput(raw: unknown): DeleteFileInput;
export declare function parseReadChunkNeighborsInput(raw: unknown): ReadChunkNeighborsInput;
/**
 * Validate `sync_start` arguments. The tool is legitimately callable with no
 * arguments — an omitted `path` means "every configured base directory" — so
 * both `undefined` and `{}` are accepted, the same contract `list_files` has.
 *
 * Root containment is deliberately not checked here: the sync core owns that
 * rule so the CLI and MCP surfaces cannot drift apart.
 */
export declare function parseSyncStartInput(raw: unknown): SyncStartInput;
/**
 * Validate `sync_status` arguments. `jobId` is required; an unknown but
 * well-formed id is the handler's concern, not this boundary's.
 */
export declare function parseSyncStatusInput(raw: unknown): SyncStatusInput;
//# sourceMappingURL=tool-input.d.ts.map