Skip to content

fix: default untyped MCP parameter root schemas to object - #894

Draft
GUANGDIJI wants to merge 1 commit into
MemTensor:v1.2.7from
GUANGDIJI:codex/fix-mcp-schema-type-v127-pr
Draft

GUANGDIJI wants to merge 1 commit into
MemTensor:v1.2.7from
GUANGDIJI:codex/fix-mcp-schema-type-v127-pr

Conversation

@GUANGDIJI

@GUANGDIJI GUANGDIJI commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Default a normalized MCP tool parameter root to type: "object" when its root type is absent, and add a focused regression test. Preserve explicitly typed root schemas and nested normalization.

Scope correction

This change does not resolve the reported multi-turn ***.type error. A live reproduction identified the upstream error field as input.type; it also occurs without tools. The cloud test Chat-to-Responses bridge emits history message items without an explicit type: "message". Paired live requests fail without that field and succeed with it on the same selected model. The corresponding backend fix is memmy-backend MR #72, targeting test (commit 4e2c76b2; 107 protocol and HTTP integration tests passed).

Keep this PR as a separate schema hardening change rather than treating it as resolution of the reported conversation failure.

Validation

  • 84 targeted Agent tests passed across MCP tool, transient retry, and probe tests.
  • Expanded four-file run: 95 passed, 12 failed in mcp-connection.test.ts (four sandbox-denied loopback listeners; eight configuration mock failures).
  • One commit and two files against v1.2.7; local and published trees match.

@GUANGDIJI GUANGDIJI changed the title fix: normalize untyped MCP tool parameter schemas fix: default untyped MCP parameter root schemas to object Nov 12, 2026
@GUANGDIJI
GUANGDIJI marked this pull request as draft November 12, 2026 06:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant