import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
/**
 * Starter recipes.
 *
 * A client that connects to this server sees north of a hundred tools and no
 * indication of where to begin, which is a real barrier for someone whose first
 * question is "what do I even ask it?". MCP prompts are the protocol's answer:
 * clients surface them as ready-made commands, so the first useful action is a
 * pick from a list rather than a blank line.
 *
 * Each one declares the tools it needs. Registration is skipped when those
 * tools are not registered -- offering "delete every stale backup" to a
 * read-only install would be an invitation to an error message.
 */
export type PromptRecipe = {
    name: string;
    title: string;
    description: string;
    /** Every tool this recipe needs. All must be registered for it to appear. */
    requires: string[];
    body: string;
};
/**
 * Note on shape: Proxmox lists guests and tasks *per node*, not cluster-wide
 * (`/nodes/{node}/qemu`, `/nodes/{node}/lxc`, `/nodes/{node}/tasks`). So every
 * recipe that spans the installation has to start by listing nodes and then
 * iterate. Saying so in the prompt is not hand-holding: without it the model
 * looks for a cluster-wide inventory call that does not exist.
 */
export declare const promptCatalog: PromptRecipe[];
export declare const applicableRecipes: (registeredTools: ReadonlySet<string>) => PromptRecipe[];
export declare const registerPrompts: (server: McpServer, registeredTools: ReadonlySet<string>) => number;
//# sourceMappingURL=prompts.d.ts.map