[Parser] Pass request.tools to tool parser

[sfeng33]

Purpose

Pass request.tools to tool parser in _WrappedParser so non-streaming Responses API tool calls work correctly for parsers that depend on self.tools. Follow up to comment in #38189

Test plan

Triggered response api on non-stream path and validated parser.tool_parser.tools is set

vllm serve Qwen/Qwen3-0.6B --enable-auto-tool-choice --tool-call-parser hermes

curl -s http://localhost:8000/v1/responses \
  -H "Content-Type: application/json" \
  -d '{
    "model": "Qwen/Qwen3-0.6B",
    "stream": false,
    "input": "What is the weather in San Francisco?",
    "tools": [
      {
        "type": "function",
        "name": "get_weather",
        "description": "Get the current weather for a location",
        "parameters": {
          "type": "object",
          "properties": {
            "location": {"type": "string", "description": "City name"}
          },
          "required": ["location"]
        }
      }
    ]
  }'

[gemini-code-assist]

Code Review

This pull request updates the parser instantiation logic to support tool definitions by passing request.tools from the serving layer to the parser. Specifically, _WrappedParser in vllm/parser/abstract_parser.py now accepts an optional list of tools and forwards them to the underlying tool parser. A review comment suggests adding *args and **kwargs to the _WrappedParser constructor to maintain compatibility with the base class and prevent potential TypeError issues in the future.

[bbrowning]

The change is small and definitely looks right on the surface. Is there any unit test or manual test you ran that verifies self.tools is now getting wired in properly for non-stream Responses API requests (I believe that's the code path that goes through the changed code)?

[sfeng33]

The change is small and definitely looks right on the surface. Is there any unit test or manual test you ran that verifies self.tools is now getting wired in properly for non-stream Responses API requests (I believe that's the code path that goes through the changed code)?

Thanks, updated the test plan with steps to trigger the response api non-stream path.

[sfeng33]

@aarnphm can you please add the ready tag?