@jupiterone/jupiterone-mcp/dist/server/tools/result.d.ts

Model Context Protocol server for JupiterOne account rules and rule details

import type { ToolResult } from './types.js';
/**
 * Builds a success result with both channels (P1):
 * - `structuredContent`: the typed payload — for code-mode consumers and future MCP Apps UI
 *   (it becomes the UI's data prop), validated against the tool's outputSchema by the SDK.
 * - `content`: the same payload as JSON text — the model-facing and text-only-host fallback the
 *   spec requires ("tools MUST return a meaningful content array even when UI is available").
 *
 * The two channels are semantically equivalent (per SEP-1624); clients choose which to forward to
 * the model. Error paths do NOT use this — they return content-only `isError` results, which the
 * SDK exempts from output-schema validation.
 */
export declare function structuredResult(payload: Record<string, unknown>): ToolResult;
//# sourceMappingURL=result.d.ts.map