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: the per-connection counterpart to `list-configured-connections`.
 * Given one `connectionId`, returns its non-secret config card plus which
 * connection-routable tools are enabled on it and, for those that aren't, the
 * reason each is gated off.
 *
 * The enabled/disabled split is read from each handler's
 * {@link import("../../../../confluent/tools/base-tools.js").ToolHandler.connectionVerdicts}
 * indexed at the requested connection — the same source `explain-disabled-tools`
 * consumes. The read-only overlay therefore needs no special-casing here: a
 * mutating tool on a `read_only` connection surfaces in the
 * {@link ToolDisabledReason.ReadOnlyConnection} bucket automatically, kept
 * distinct from the service-block-missing buckets, and the text summary renders
 * that bucket affirmatively as the set of writes the flag suppresses.
 *
 * Always enabled (predicate is `alwaysEnabled`) so an operator can introspect a
 * connection even when its config left every routable tool disabled. The
 * connection-routability filter and the catalog thunk both come from
 * {@link ToolMetadataHandler}.
 */
export declare class DescribeConfiguredConnectionHandler 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=describe-configured-connection-handler.d.ts.map