cap_web_search
Source: cap_web_search.ccomponents/claw_capabilities/cap_web_search/src/cap_web_search.c · header: cap_web_search.hcomponents/claw_capabilities/cap_web_search/include/cap_web_search.h · Skill: SKILL.mdcomponents/claw_capabilities/cap_web_search/skills/cap_web_search/SKILL.md
Overview
Section titled “Overview”cap_web_search exposes the web_search tool to the LLM, allowing the Agent to run web searches through the configured search provider. It currently supports two search API backends: Tavily and Brave Search.
Tool description
Section titled “Tool description”| Tool ID | Description |
|---|---|
web_search | Search the web and return concise formatted results |
Input parameters
Section titled “Input parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search keywords |
Return value
Section titled “Return value”Returns formatted search result text containing titles, summaries, and links. By default it returns the first 5 results.
Search providers
Section titled “Search providers”| Provider | NVS config key | Description |
|---|---|---|
| Tavily | tavily_api_key | Preferred provider; if both Tavily and Brave are configured, Tavily is used first |
| Brave Search | brave_api_key | Fallback provider |
Registration and configuration
Section titled “Registration and configuration”API keys are usually read from NVS by the application layer, then passed to the corresponding set_*_key function.
Group information
Section titled “Group information”| Property | Value |
|---|---|
| Group ID | cap_web_search |
| Default LLM-visible | Yes (edge_agent default initial visible group) |
| Tool count | 1 |