/**
 * [WHO]: MCP_SERVER_HINTS, getMcpServerHint(), getMcpServerScenarios()
 * [FROM]: Depends on nothing — pure data + lookup helpers.
 * [TO]: Consumed by core/mcp/mcp-adapter.ts (buildMcpToolGuidance / buildMcpDescriptionSuffix).
 * [HERE]: core/mcp/mcp-server-hints.ts - per-server scenario vocabulary for guidance text.
 *
 * Each hint entry maps a builtin MCP server id (from mcp-config.ts) to a
 * short list of user-facing scenario phrases. The phrases are intentionally
 * phrased as observable user intents ("read files outside the local project
 * cwd", "fetch a public web page") so that when merged into the LLM's
 * guidance / description text they raise the chance the model recognizes
 * a query → tool match it would otherwise miss.
 *
 * Server ids not present here fall through to a generic "<serverId>'s domain"
 * phrase. Adding a new server to mcp-config.ts without a hint entry is fine;
 * the hint layer degrades gracefully.
 *
 * Keep entries short and concrete. Verbose marketing copy wastes prompt
 * budget and dilutes signal across many tools.
 */
export declare const MCP_SERVER_HINTS: Record<string, readonly string[]>;
/**
 * Get the scenario phrases for a server id. Returns an empty array for
 * unknown servers — callers must handle the empty case.
 */
export declare function getMcpServerScenarios(serverId: string): readonly string[];
/**
 * Get a short hint phrase for a server id, suitable for embedding in
 * guidance / description text. Falls back to "<serverId>'s domain" when
 * no scenario list is registered. Length is bounded to keep the resulting
 * guidance under the ~280-char budget enforced by the system-prompt MCP
 * section verifier.
 */
export declare function getMcpServerHint(serverId: string): string;