Catalog and inspection
list_tools
list kernel and enabled verba tools for current portal
Built-in capabilities
Kernel tools are Tater's native action layer.
They handle files, web inspection, memory, artifacts, delivery, and optional Spudex terminal console work before Hydra reaches for a Verba.
Kernel tools
Catalog and inspection
Kernel tools
Workspace and files
Workspace and files
attach_file
attach an available artifact/local file and optionally send it to a destination platform/target
Workspace and files
delete_file
delete a local file
Workspace and files
download_file
download a file from a concrete file URL after discovery/inspection (actual file retrieval)
Workspace and files
extract_archive
extract archives to a target directory
Workspace and files
list_archive
inspect archive entries
Workspace and files
list_directory
list files and folders
Workspace and files
read_file
read local file contents
Workspace and files
search_files
search text across local files
Workspace and files
write_file
write content to a local file
Kernel tools
Web and media
Web and media
image_describe
describe an explicit image using an artifact_id, URL, blob, or local path
Web and media
inspect_webpage
inspect and extract content from a specific webpage URL (title, summary text, links, images)
Kernel tools
Memory and delivery
Memory and delivery
send_message
queue a cross-portal notification/message only when the user explicitly asks to notify or message a destination (never for normal chat replies)
Kernel tools
Terminal console
Terminal console
Spudex tools are conditional kernel tools.
The spudex_run, spudex_task, spudex_status, and spudex_stop tools appear to Hydra only when Spudex is enabled for the active platform. Configure them from the Spudex tab, then use the dedicated Spudex docs for policy, session, and direct-chat behavior.
Web search setup
How to enable modular search providers for the search_web kernel tool.
This is a core capability, not a Verba. Download and enable providers from Settings -> Integrations.
SearXNGBrave SearchGoogleSerper
Pick a provider
The search_web kernel tool now discovers enabled web-search integrations.
- Open Settings -> Integrations, download the provider you want, then enable it from Manage.
- Tater currently ships downloadable providers for SearXNG, Brave Search, Google Custom Search, and Serper.
- You can enable more than one provider; Tater tries enabled web_search integrations in configured order.
Settings -> IntegrationsSetupTest
Provider settings
Each provider owns its own settings and test action.
- SearXNG needs the instance URL and optional bearer token.
- Brave Search and Serper need their API keys.
- Google Custom Search needs both a Google API key and Programmable Search Engine CX value.
Capability discoveryProvider orderFallback
How Tater chooses
Search providers advertise the shared web_search capability.
- search_web asks the integration registry for enabled providers with the web_search capability.
- Providers are sorted by order, then stable provider name/id, so equal orders are deterministic.
- If a provider is not configured or fails, Tater can continue to the next enabled provider.
querysitecountrylanguage
What the kernel tool supports
The search_web input shape stays the same even when providers change.
- query is required, while num_results, start, site, safe, country, and language are optional.
- site narrows results to one domain when the provider supports it.
- Hydra can keep using search_web without caring which provider integration is currently enabled.