Issue evidence · Serve · vllm-project/vllm

Gemma4 on vLLM + PI coding agent: Validation failed for tool "edit": path must have required property

GitHub issue: https://github.com/vllm-project/vllm/issues/39072

Not run

Gemma 4 31B omits the required path argument when calling the edit tool through vLLM's gemma4 tool parser.

What Badgr ran

Tried to serve google/gemma-4-31B-it (31B, about 62 GB, not gated) on an A100 80GB through Badgr with vLLM 0.30.0 and --tool-call-parser gemma4, to send 30 requests with the PI agent's edit tool schema. The deployment failed on provider capacity (provider_capacity_failed) before the server became healthy.

What came back

  • No requests were sent, so the missing path argument was not tested.
  • The report's received arguments show a malformed newText beginning with an escaped string delimiter, which points at the parser, not only at the model.

Not run to a result: the A100 route never became healthy. A rerun on any 80 GB GPU with the same 30-request script would settle it.

Checked 2026-10-15 in Badgr’s local development environment.

← All issue evidence