import { CallToolResult } from "../../../../confluent/schema.js";
import { ToolCategory, ToolConfig } from "../../../../confluent/tools/base-tools.js";
import { ToolMetadataHandler } from "../../../../confluent/tools/tool-metadata-handler.js";
import { ServerRuntime } from "../../../../server-runtime.js";
/**
 * Discovery tool: maps each configured connection id to the tools an agent can
 * actually invoke against it. "Actually invokable" means a tool both survived
 * the operator's allow/block-list and whose predicate enables that specific
 * connection — the same two gates tool registration applies, so this listing
 * can never claim a tool the server didn't advertise.
 *
 * This tool itself is always enabled (predicate = `alwaysEnabled`) but intentionally excludes
 * connection-agnostic tools from the per-connection lists: a tool whose predicate is `alwaysEnabled`
 * applies to every connection, so listing it under each connection would misrepresent it as
 * connection-routable. This tool answers "which connections are available and which tools
 * are directly usable on each."
 *
 * The tool catalog is supplied through the thunk that {@link
 * ToolMetadataHandler} owns, for the ESM-cycle reason documented there.
 */
export declare class ListConfiguredConnectionsHandler extends ToolMetadataHandler {
    handle(runtime: ServerRuntime, toolArguments?: Record<string, unknown>): CallToolResult;
    getToolConfig(): ToolConfig;
    readonly category = ToolCategory.McpServerDiagnostics;
    readonly predicate: import("../../../../confluent/tools/connection-predicates.js").ConnectionPredicate;
}
//# sourceMappingURL=list-configured-connections-handler.d.ts.map