PR #63634: fix: accept valid MCP tool schemas without strict inputSchema.type check

• Repository: openclaw/openclaw
• Author: zozo123
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/63634

Description (problem / solution / changelog)

Summary

Fixes MCP server loading failure when tools have inputSchema without explicit type: "object".

Closes #63602

Changes

• Replace client.listTools() with client.request() using a lenient Zod schema (LenientListToolsResultSchema) that accepts inputSchema as any record rather than requiring type: z.literal("object")
• Add normalizeInputSchema() to ensure the catalog always contains type: "object" after listing, so downstream LLM providers receive valid tool definitions
• Existing tools with type: "object" are passed through unchanged (no-op path)

Root Cause

The MCP SDK v1.29.0 ToolSchema validates inputSchema.type as z.literal("object"). Some MCP servers (especially those using older SDKs or custom implementations) omit the type field from their inputSchema, returning e.g. { properties: { ... } } without type: "object". This causes a Zod validation error: invalid_value expected "object" in inputSchema.type.

Testing

• All 23 existing tests across 4 test files pass (runtime, materialize, plugin-tools-serve, schema)
• The fix is backward-compatible: servers that already return type: "object" are unaffected
• TypeScript compilation passes with no errors

This PR was generated with AI assistance (Claude).

Changed files

• src/agents/pi-bundle-mcp-runtime.test.ts (modified, +28/-0)
• src/agents/pi-bundle-mcp-runtime.ts (modified, +45/-5)