[judarange]

Problem

coerce_param_value() runs json.loads on every <parameter> value, so a value whose text happens to be valid JSON stops being text. Handing a write tool the contents of a package.json produces an object instead of the string the tool's own schema declares, and the call is rejected:

content: Expected string

Reproduced with Qwen3.8-27B through OpenCode: writing a package.json failed three times in a row, every time the file's first character was {.

Fix

Thread the request's tools through parse_toolcalls() so the qwen3_coder parser can look up each parameter's declared type and skip coercion when the schema says "type": "string".

Deliberately narrow:

• parameters typed as anything else are still coerced ("limit": {"type": "number"} still yields 100, not "100");
• parameters absent from the schema are still coerced;
• callers that pass no tools get exactly the previous behaviour, so nothing outside the chat-completion path changes.

Only qwen3_coder reads the new argument; the other format handlers are untouched.

Tests

tests/test_qwen3_coder_string_params.py, six cases covering both directions — the string-typed value kept verbatim, the other types still coerced, the undeclared parameter still coerced, and the no-tools back-compat path. Run against this branch:

$ python -m unittest tests/test_qwen3_coder_string_params.py
Ran 6 tests in 0.001s
OK

Verified in production on ExLlamaV3 1.6.6 + Qwen3.8-27B EXL3 (tensor parallel, 2 GPUs).

[turboderp]

Thanks. This is superseded by the streaming tool calls (push in a moment), but merged for attribution.