Bash tool calling fails with GLM5.1 on prem

[rememberSoftwares]

Description

Getting

$ ls -la
The bash tool was called with invalid arguments: [
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "description"
    ],
    "message": "Invalid input: expected string, received undefined"
  }
].
Please rewrite the input so it satisfies the expected schema.

Using GLM5.1 on prem as backend.

Everything was find with GLM5 though...

---

The tool output is shown in the TUI but the LLM doesn't recieve it:

> Do whomai
Thinking: The user wants to run whoami.
# Show current user
$ whoami
elancelot
Thinking: The bash tool is still not returning any results. This seems like a persistent issue with the tool execution environment. Let me try a different approach.
The bash tool continues to return empty results. This appears to be an environment issue. You can run whoami directly in your terminal to see your current user.

Using Opencode 1.4.3
The error is happening on linux/mac and various opencode versions. The error seems to be related to GLM5.1 and how opencode interacts with this model specificaly.

Plugins

No response

OpenCode version

1.4.3

Steps to reproduce

Connect to GLM5.1 onprem

Screenshot and/or share link

No response

Operating System

Linux/Mac

Terminal

Terminator / Mac default shell

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Bash(ls -la) tool description parameter is required but not exposed in tool schema — breaks all bash calls #13146: Same exact error — bash tool description parameter validation fails with expected string, received undefined
• bash description #17415: Same error message with bash tool description field on a different model/OS
• Bash tool called with invalid arguments: "expected string, received undefined" for command and description fields #14519: Same bash tool invalid arguments error for description field

The core error you're seeing (expected string, received undefined for the description path) appears to be a known issue with certain models not passing the description parameter when calling the bash tool. The GLM5.1-specific behavior (tool output not being received by the LLM) may be a related or separate issue — #6708 covers GLM-series tool call quirks.

[rememberSoftwares]

Issue #13146 may indeed be a duplicate.