Generate eval cases from the suite's tools
Discovers the suite’s server tools over a live MCP connection, generates cases against them, and persists them — the only edit route that connects to a server, and the only one that SPENDS ORG CREDITS. Synchronous: connect, generate, persist, disconnect, respond.
An environment-based suite generates against that environment’s closed server set, so the cases match the tools its runs will actually see.
Pass x-mcpjam-idempotency-key to make a retry safe: drafts are recorded backend-side BEFORE any case is persisted, so a replay reuses them instead of spending credits again, and each case is persisted under a derived per-item key so the loop is resumable.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Headers
Makes a retry replay the recorded drafts instead of spending credits again.
Path Parameters
ID of the hosted project that contains the server.
Eval suite ID, as returned by POST /eval-runs.
Body
AI-generate cases from the suite's server tools and persist them. SPENDS ORG CREDITS.
Superseded by caseMix when that is present.
normal, negative Server ids or names to discover tools from. Ignored when the suite is environment-based.
1Discover tools from this attached environment's closed server set, so generated cases are written against the tools the suite's runs will actually see.
1Per-bucket case counts. Omitted buckets inherit the default mix; the backend bounds each bucket and the total.
Condition generated cases on a range of user styles so the queries read like different users wrote them.

