/**
 * File delivery tools — agent-facing affordances for files PICA already
 * holds.
 *
 * The upload side (getting files INTO PICA) is covered by pica_upload (the
 * MCP-Apps card), pica_upload_file (programmatic presigned PUT), and the
 * audio-specific pica_audio_presigned_upload.
 *
 * The download side is intentionally **not** raw presigned URLs. Deliveries
 * are first-class records — each one binds a file id to a specific
 * recipient email, carries a token + expiry, and can be revoked. That gives
 * the org an audit trail of who received what and when, and a kill switch
 * if a link leaks. Wraps the routes under `/admin/files/deliver`.
 *
 *   - pica_file_deliver        → generate a delivery link for a recipient
 *   - pica_file_revoke_delivery → revoke a previously-issued link
 */
import { PicaClient } from "@withpica/mcp-sdk";
import { ToolDefinition, ToolExecutor } from "./index.js";
export declare class FilesTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private deliver;
    private revoke;
}
//# sourceMappingURL=files.d.ts.map