Skills 2026-10-11 03:36 UTC
summerv3.5.2
Version [3.5.2] committed by mathias-heide. Update Category: Bug Fixes & Stability Improvements. Commit details: Tool schemas strict providers accept: fixes Kimi Code HTTP 400 (3.5.2) (#102). This update resolves known runtime errors and enhances system reliability.
CommitRaw commit message
Tool schemas strict providers accept: fixes Kimi Code HTTP 400 (3.5.2) (#102)
* MCP tool schemas use the JSON Schema subset strict providers accept (Kimi 400 fix)
Kimi Code forwards each tool's inputSchema to Moonshot, which rejected the
whole request with HTTP 400 ("items must be an object") on the tuple axis
of summer_align_distribute_3d. Ten tools published z.tuple vectors as an
array of schemas in items, and reused zod values became $ref pointers into
the same schema with no definitions.
tools/list now passes every inputSchema, local and hosted, through
providerSafeSchema: a tuple becomes an array with one items schema and
exact minItems/maxItems, local $refs are inlined, and a type array becomes
anyOf. zod still validates every call, so a wrong-length vector is still
rejected.
provider-safe-schema.test.ts walks the real tools/list and fails on tuple
items, prefixItems, additionalItems, $ref, type arrays, unsupported formats
or keywords outside the strict subset.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Release 3.5.2: tool schemas Kimi Code and other strict providers accept
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Provider-safe schemas also drop non-strict formats and string-only propertyNames
The hosted store tools are zod 4 output: z.string().url() publishes
format "uri" and z.record(z.string(), ...) publishes propertyNames
{type: string}, both outside OpenAI strict mode's subset. The rewrite now
walks only real subschema positions, so a property named format, items or
propertyNames is left alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>