bottlenecks-mcp-server/lib/tools/image-operations.d.ts

Model Context Protocol server for Bottlenecks database - enables AI agents like Claude to interact with bottleneck data

/**
 * MCP Image Operations Tools
 * Lets AI agents generate a cover image for a bottleneck. Deliberately kept
 * separate from create_bottleneck / update_bottleneck — creating or editing a
 * bottleneck never silently triggers a paid image generation call; an agent
 * must call this tool on its own. This thin wrapper calls /api/images/generate
 * over HTTP (same pattern as every other tool in this file set) — that route
 * is itself generated from the single @supernal/universal-command definition
 * in lib/images/commands.ts, so this is not a second implementation of the
 * generation logic, just its MCP-facing transport.
 */
import { MCPTool } from '../types/mcp.js';
import { MCPOAuthClient } from '../auth/oauth-client.js';
/**
 * Generate a cover image for an existing bottleneck.
 *
 * Guardrail: the API enforces a cap (default 1) on how many generated images
 * a single bottleneck can accumulate. Exceeding it requires `confirm: true`
 * — deliberately NOT defaulted to true, so an agent has to consciously ask
 * to replace/add another image rather than looping past the cap by accident.
 */
export declare function createGenerateBottleneckImageTool(client: MCPOAuthClient): MCPTool;
/**
 * Upload or link an already-available image for a bottleneck — the DIY
 * alternative to generate_bottleneck_image. No per-entity cap: a deliberate
 * upload isn't the runaway-cost risk that repeated generation calls are.
 */
export declare function createUploadBottleneckImageTool(client: MCPOAuthClient): MCPTool;
/**
 * Delete a bottleneck's current image. Completes the CRUD set alongside
 * generate_bottleneck_image (create/generated) and upload_bottleneck_image
 * (create/uploaded).
 */
export declare function createDeleteBottleneckImageTool(client: MCPOAuthClient): MCPTool;
//# sourceMappingURL=image-operations.d.ts.map