"j8SrSSKJr SSKJrJrJr SSKJr SSK J r J r J r SSK JrJr SSKJrJrJr S S KJr \ (aSS KJr /S Qr\ S r\ Sr\\\\\\S/\\\\\-4r\ \\\\4rSr\"SS9"SS\55rg)aInternals for the tool-search native tool. Tool search lets the model discover tools marked with `defer_loading=True` rather than carrying every deferred tool's full schema in the prompt. The [`ToolSearch`][pydantic_ai.capabilities.ToolSearch] capability picks between three modes per provider: * **Native server-side**: the provider's own tool-search tool (Anthropic `bm25`/`regex`, OpenAI server-executed `tool_search`). * **Native client-executed (custom callable)**: the provider invokes our local callable through its native client-execution mode (Anthropic regular function tool + `tool_reference` result blocks, OpenAI `ToolSearchToolParam(execution='client')`). * **Local fallback**: a regular `search_tools` function tool the model can call. Used on providers that don't expose any native tool-search surface. The end-user surface is the [`ToolSearch`][pydantic_ai.capabilities.ToolSearch] capability; the types in this module are kept here as implementation detail. ) annotations) AwaitableCallableSequence) dataclass) TYPE_CHECKINGLiteralUnion) AgentDepsT RunContext)ToolSearchArgsToolSearchMatchToolSearchReturnContent)AbstractNativeTool)ToolDefinition)rrrToolSearchNativeStrategyToolSearchLocalStrategyToolSearchFuncToolSearchStrategyTOOL_SEARCH_FUNCTION_TOOL_NAME)bm25regexkeywordsr search_toolsT)kw_onlyc8\rSrSr%SrSrS\S'SrS\S'S rg) ToolSearchToolfuFramework-internal: users access tool search via the [`ToolSearch`][pydantic_ai.capabilities.ToolSearch] capability — do not construct directly. A native tool that enables provider-side tool search. Tools marked as part of the search corpus (via `with_native='tool_search'` on their [`ToolDefinition`][pydantic_ai.tools.ToolDefinition]) are sent to supporting providers with `defer_loading` on the wire; the provider manages their visibility and only exposes them once they've been discovered. The mode of discovery depends on `strategy`: * A named native strategy (or `None` for the provider default): the provider runs the search server-side using its own indexing (Anthropic `bm25`/`regex`, OpenAI server-executed `tool_search`). * `'custom'`: the provider invokes our local search function to answer each search request. On Anthropic this goes via a regular function tool whose return value the adapter re-formats as `tool_reference` blocks; on OpenAI it goes via `ToolSearchToolParam(execution='client')` with our callable's parameter schema. When the model doesn't support native tool search at all, the [`ToolSearch`][pydantic_ai.capabilities.ToolSearch] capability's local implementation handles discovery via its own `search_tools` function tool. Supported by: * Anthropic (bm25, regex, custom callable) — Sonnet 4.5+, Opus 4.5+, Haiku 4.5+ * OpenAI Responses (server default, custom callable via `execution='client'`) — GPT-5.4+ (named strategies `'bm25'`/`'regex'` are not supported). Nz)Literal['bm25', 'regex', 'custom'] | Nonestrategy tool_searchstrkind) __name__ __module__ __qualname____firstlineno____doc__r!__annotations__r$__static_attributes__r%b/home/mande/repo/quber/.venv/lib/python3.13/site-packages/pydantic_ai/native_tools/_tool_search.pyrrfs(<;?H7>(D#r-rN) r* __future__rcollections.abcrrr dataclassesrtypingrr r _run_contextr r messagesrrrrtoolsr__all__rrr#rrrrr%r-r.r8s&#99!001OO & #?3"*- Xc]H5E,FG SMIhsm,,.>*57NPhhi "0)  45'55r-