bifrost-code-modelisted

# Bifrost code mode Most servers on a Bifrost gateway are **not** flat tools. They do not appear in your tool list and `mcp__bifrost__<server>-<tool>` does not exist for them. They are reached by writing a short Starlark snippet and running it with `executeToolCode`. If a capability seems missing, it is almost certainly here. Do not conclude the gateway lacks it, and do not fall back to guessing from training data, until you have checked. ## The four meta-tools Exact schemas, as the gateway advertises them: | Tool | Parameters | Required | |---|---|---| | `listToolFiles` | *(none)* | — | | `readToolFile` | `fileName`, `startLine`, `endLine` | `fileName` | | `getToolDocs` | `server`, `tool` | both | | `executeToolCode` | `code` | `code` | The parameter is `fileName`, **not** `path` or `file`. Passing `path` fails with `fileName parameter is required and must be a string`. `fileName` is the full catalog path: `servers/<server>/<tool>.pyi`. ## Workflow **1. Discover.** `listToolFiles()` returns the catalog, grouped by server: ``` servers/ jira/ search_jira_tickets.pyi create_jira_ticket.pyi ... ``` **2. Confirm the signature.** Never call a tool whose parameters you have not read. ``` readToolFile(fileName="servers/jira/search_jira_tickets.pyi") ``` returns a typed stub with the exact callable name and an inline description: ```python # Total lines: 10 (this is the complete file, no need to paginate) # jira.search_jira_tickets tool # Usage: jira.tool_