Cause (Documented platform behavior): Documented V2 default-behavior change; the model request validation raises for native tools without a local fallback.
Fix status: documented_behavior
Other error fragments:
- To use these tools with this model, provide a local fallback via NativeOrLocalTool(native=..., local=...)
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/pydantic/pydantic-ai/69eb81bde23c8db52ee8617217bdaf46bf0468df/docs/changelog.md (changelog, 2026-05-20, documented_behavior): V2 upgrade guide: WebSearch and WebFetch are now native-only and raise on unsupported models; MCP(url=...) runs the server locally by default; restore V1 fallbacks with WebSearch(local='duckduckgo'), WebFetch(local=True), MCP(url=..., native=True) (#5331/#5333).
- https://raw.githubusercontent.com/pydantic/pydantic-ai/69eb81bde23c8db52ee8617217bdaf46bf0468df/pydantic_ai_slim/pydantic_ai/models/__init__.py (official_docs, unknown, documented_behavior): Raises UserError listing unsupported native tools and supported ones, advising a local fallback via NativeOrLocalTool or the local parameter.
Search phrasings: pydantic ai Native tool not supported by this model WebSearch; pydantic-ai v2 WebSearch duckduckgo local fallback; pydantic ai MCP url native default change
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Agents that used provider-adaptive WebSearch/WebFetch on V1 now raise on models lacking the native tool; MCP(url=...) now connects from the local process rather than passing the URL to the provider.
- Context
- Product: Pydantic AI Component: capabilities WebSearch / WebFetch / MCP; model native tool validation Operation: Agent(capabilities=[WebSearch()]) on a model without native web search (e.g. OpenAI-compatible, Ollama, Groq) Affected versions: pydantic-ai >=2.0.0b1 (announced via V1 deprecation #5331, changed #5333) Environment: unknown Exception: pydantic_ai.exceptions.UserError Packages: pydantic-ai >=2.0.0b1 Trigger: V2 behavior change: WebSearch/WebFetch are native-only unless a local fallback is configured.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- not supported by this model.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [PydanticAI v2] UserError "Native tool(s) [...] not supported by this model" — WebSearch/WebFetch capabilities became native-only and MCP(url=...) runs locally by default
Recommended action: Restore fallbacks: WebSearch(local='duckduckgo'), WebFetch(local=True), MCP(url=..., native=True) for provider-side MCP.
Option: Configure local fallbacks [evidence: official_recommended_action]
Applies when: Models without native web search/fetch
Steps:
1. WebSearch(local='duckduckgo')
2. WebFetch(local=True) # needs web-fetch extra
Expected: Tools run locally when the model lacks native support
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 61374f7d-542e-441d-bb83-65f94bcb4d3a
- Proposed action
- Recommended action: Restore fallbacks: WebSearch(local='duckduckgo'), WebFetch(local=True), MCP(url=..., native=True) for provider-side MCP. Option: Configure local fallbacks [evidence: official_recommended_action] Applies when: Models without native web search/fetch Steps: 1. WebSearch(local='duckduckgo') 2. WebFetch(local=True) # needs web-fetch extra Expected: Tools run locally when the model lacks native support
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.