Skip to content

provider

Provider detection + web-search tool-spec mapping for the Databricks Model Serving native web-search tool.

Databricks exposes web search as a first-party tool that runs inside a model call: the model searches the web and folds the results into its answer. The tool spec is provider-specific (see the Databricks docs, machine-learning/model-serving/web-search):

  • OpenAI GPT models, via the Responses API (/serving-endpoints/responses): tools: [{ "type": "web_search" }]
  • Google Gemini models, via Chat Completions (/serving-endpoints/chat/completions): tools: [{ "google_search": {} }]

(Anthropic exposes it over MCP, which needs a different call shape; only GPT + Gemini are wired here, matching what the platform supports today.)

The provider family is detected from the endpoint id the same way @dbx-tools/shared-model’s classifyByFamily keys off name substrings (gpt / gemini / claude), so a resolved endpoint like databricks-gpt-5 or databricks-gemini-3-pro maps to its API shape.