[ENHANCEMENT] allow support of native tool call for Open Ai Compatible

[bozoweed]

Problem (one or two sentences)

Curretly Open Ai Compatible only accept XML for tool usage that restrain us for tool call quality

Context (who is affected and when)

Open Ai compatible on model that support tool calling

Desired behavior (conceptual, not technical)

allow Open Ai Compatible to switch from xml format to tool call native

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Problem Analysis

Currently, the OpenAI Compatible provider (used when apiProvider is "openai") only supports XML format for tool usage. This limits tool call quality for models that support native OpenAI-style tool calling.

Proposed Solution

Add support for native tool calling format to the OpenAI Compatible provider, allowing users to choose between XML and native formats based on their model's capabilities.

Implementation Plan

1. Add UI Toggle for Tool Protocol Selection

• Add a checkbox in webview-ui/src/components/settings/providers/OpenAICompatible.tsx to allow users to select between XML and native tool protocols
• Similar to the "Use Legacy Format" option, add "Use Native Tool Calling" option
• Store this preference in the provider settings

2. Update Provider Settings Schema

• The toolProtocol field already exists in baseProviderSettingsSchema (line 189 in packages/types/src/provider-settings.ts)
• No schema changes needed, just need to expose it in the UI

3. Update BaseOpenAiCompatibleProvider

• The provider already supports native tools (lines 96-100 in src/api/providers/base-openai-compatible-provider.ts)
• Tool protocol is resolved via resolveToolProtocol() function which checks:
  1. User preference (profile setting)
  2. Model default
  3. Falls back to XML
• The implementation is already there, just needs UI exposure

4. Add Model Capability Flag

• Update openAiCustomModelInfo to include a supportsNativeTools boolean field
• This allows users to specify if their custom OpenAI-compatible model supports native tool calling

5. Update Translations

• Add appropriate translation keys for the new UI elements in the localization files

Benefits

• Improved tool calling quality for OpenAI-compatible models that support native format
• Better compatibility with various OpenAI-compatible providers (LocalAI, vLLM, etc.)
• User control over tool protocol selection based on their specific model capabilities

Testing Approach

• Test with models that support native tools to ensure proper formatting
• Test with models that don't support native tools to ensure XML fallback works
• Verify the UI toggle properly saves and loads the preference

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[hannesrudolph]

this is a bug. it should show up but currently only shows up when you create a new api profile.

[bozoweed]

in case if not spawning we need to create new profile switch to Open Router, save close, open setting create new again switch on Open ai compatible and because uri is not setup we can have the new selector

[hannesrudolph]

@bozoweed there this should do the trick. Should be released within the hour.