/**
 * ADR-406 §19.7 — MCP adapter for the mission semantic operations.
 *
 * A thin transport: input goes to the same `MissionService` (and the same zod
 * schemas) the CLI uses, unchanged. Policy authorization of the tool call
 * itself happens in `mcp-client.ts` before any handler runs; nothing here
 * accepts an approval, principal or permission flag from input.
 */
import type { MCPTool } from './types.js';
import { type MissionResult } from '../missions/service.js';
/** The operations an adapter needs; London-school tests substitute it. */
export interface MissionPort {
    create(raw: unknown): Promise<MissionResult<unknown>>;
    plan(raw: unknown): Promise<MissionResult<unknown>>;
    get(raw: unknown): Promise<MissionResult<unknown>>;
    events(raw: unknown): Promise<MissionResult<unknown>>;
    requestAction(raw: unknown): Promise<MissionResult<unknown>>;
}
export type MissionPortFactory = (projectRoot: string) => MissionPort;
export declare function createMissionTools(factory?: MissionPortFactory): MCPTool[];
export declare const missionTools: MCPTool[];
//# sourceMappingURL=mission-tools.d.ts.map