Bug type

Behavior bug (incorrect output/state without crash)

Summary

Title

Session-Start Bug: Empty/Invalid Tool Calls on Multi-Tool Invocations

Description

Symptom

During session start or multi-tool invocations, I generate empty/invalid tool calls:

• Tool not found → sending empty string "" as tool name
• Missing required parameter: path → calling tools without required parameters

Reproduction

Happens reproducibly when:

• Multiple parallel tool calls (multi-tool)
• "Parallel thinking"
• Sometimes even during simple file reads at session start

Actual Behavior

Tool calls are generated with empty or invalid parameters, causing execution failures. The gateway logs show "read tool called without path" errors, and the tool validation fails with "Missing required parameter: path".

Expected Behavior

Tool calls should always be generated with correct parameters and valid tool names, even during parallel invocations.

Current Workaround

I have to consciously make single-step calls and isolate tool calls—this is cumbersome and limits my capability.

Steps to reproduce

• Multiple parallel tool calls (multi-tool)
• "Parallel thinking"
• Sometimes even during simple file reads at session start

Expected behavior

Tool calls should always be generated with correct parameters and valid tool names, even during parallel invocations.

Actual behavior

Tool calls are generated with empty or invalid parameters, causing execution failures. The gateway logs show "read tool called without path" errors, and the tool validation fails with "Missing required parameter: path".

OpenClaw version

2026.3.2

Operating system

Red Hat 9

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response