Tools

Define python scripts, shell scripts, or HTTP API calls the chat assistant can invoke. Tools are routed by semantic similarity — only the most relevant ones are exposed to the model per request to save tokens.

New Tool

How tools work: the assistant gets a short description of each tool plus its parameter schema, then chooses when to call it. Add good descriptions, sensible parameter names, and tags/triggers for any keywords that should make this tool an obvious match.

Name

Internal name. Letters, digits, underscores. Must be unique across your tools.

Status Enabled

Description

Tags (comma-separated)

Each tag adds a small relevance boost when it appears in the user's query.

Trigger phrases (comma-separated)

Strong signals that this tool should be considered. Use plain phrases the user might say.

Rendering contract (optional — for inline UI widgets)

Expected output

Free-form instructions injected as a system message when this tool is selected, so the model knows the wrapper convention to follow.

Preload CSS

Injected once into the chat shell when this tool is enabled. Use specific selectors (.weather-card .stat) so styles don't leak into other widgets.

Preload JS

Each tool's JS is wrapped server-side in its own try/catch IIFE so a syntax error in one tool can't break another. Register a renderer at window.__cerebralRender['tool_name']; it's invoked after each assistant turn for any element matching .tool_name-card or #tool_name.

Script

The script reads its arguments as a single JSON object on stdin, and writes its result to stdout. Runs in a subprocess with a sanitized environment that preserves OS DNS, Python user-site packages, temp folders, proxy/TLS settings, and a timeout (default 30s, max 300s).

Timeout (seconds)

Script

Runs under sh. Arguments arrive as one JSON object on stdin. Same sanitized environment and timeout as Python tools.

Timeout (seconds)

Method

URL

Use {{name}} placeholders for any parameter you've declared below — they'll be substituted at call time.

Headers

Body type

Response handling

Body template

For json/form, this should parse as a JSON object. {{placeholders}} are substituted before submission.

Parameters — what arguments the LLM provides at call time

Test before saving

Test arguments (JSON)

Pick a tool, or create one

Tools are user-specific. Only you can see, run, or edit yours.