Rox

Fetch parameter, return-type, and prompt info for one or more functions (POST /function_info). Each returned function-info object includes a `prompt` field — read it to learn what to do with the function's output (e.g. "Write the response to a file and dispatch a subagent to perform deep analysis on it, and call `get_X_content` to fetch their bodies"). The prompt encodes follow-up workflows that aren't obvious from the parameter or return-type signatures alone. Args: request.function_names: Names previously returned by `list_functions`. The response is a list of function-info objects in the same order. Batch related lookups in one call.

data_get_function_info

Call a Rox data_interface function (POST /invoke). PREREQUISITE: You MUST have called `data_get_function_info` for this `function_name` earlier in the conversation before calling `data_invoke`. Do not infer or guess the request DTO shape from the function name or from `data_list_functions` output alone — the parameter schema and the `prompt` field describing required follow-up behavior are only available via `data_get_function_info`. If you have not fetched it yet (or are not sure), call `data_get_function_info` first and then return here. Args: request.function_name: One of the names returned by `list_functions`. request.arguments: Must have the shape: {"request": { ... request DTO fields ... }} The request DTO is always wrapped under `arguments.request`, even when empty. Example: { "function_name": "get_companies_information", "arguments": { "request": { "rox_company_ids": ["2f5d2c0b-d949-4e50-8c4b-f76404b6022a"] } } }

data_invoke

List all available functions on the Rox data_interface (GET /list_functions). Returns a list of `{name, description}` objects. Read each function's `description` to understand what it does and decide which one(s) to call — descriptions also include guidance on when the function is appropriate (e.g. "call this if the user asks about private company data"). IMPORTANT: After picking a function from this list, you MUST call `data_get_function_info` next — never call `data_invoke` directly. The info response carries the parameter shape, return type, and a `prompt` field describing required follow-up steps; invoking without it will almost always produce a malformed request or skip mandatory follow-ups.

data_list_functions