/**
 * Tools the hosted demo registers but cannot serve: each reads a system the
 * demo environment does not have. On 2026-11-13 they answered a visitor's
 * agent with set-your-API-key instructions (DD_API_KEY, CLICKHOUSE_URL,
 * LOG10X_CUSTOMER_METRICS_URL) or routed it to tools the demo does not
 * expose. In the demo playground they now say so in one line instead.
 *
 * They stay registered: the deploy gate (backend .github/scripts/
 * verify-demo-mcp.py) requires the live tool list to equal the manifest
 * allowlist, and an agent that lists tools should learn what the product can
 * do on its own data.
 */
import { type StructuredOutput } from './output-types.js';
export declare function isDemoPlayground(): boolean;
/** The demo line for `tool`, or null when the tool is served in the demo. */
export declare function demoUnavailableLine(tool: string): string | null;
export declare function demoUnavailableEnvelope(tool: string): StructuredOutput | null;