Sinch Build Docs

Get the exact TypeScript signatures of the sandbox tools available to `execute`. Analyze the user request first, then pass `tools` with only the tool names the request needs (every name is listed in this input schema / description); omit `tools` only when you cannot tell which tools apply. Always call this before your first `execute` and never guess signatures. Request every tool the task may need in ONE call instead of calling this repeatedly.

Run JavaScript in a sandbox against the documentation tools on the global `tools` object. The only extra global is `tools` - there is no `fetch`, `console`, `setTimeout`, `require`, or Node.js API; all I/O goes through `tools`. Workflow - minimize round-trips; one `describe-tools` call plus one `execute` call covers most requests: 1. Analyze the request and decide which sandbox tools it needs (every tool name is listed in the `describe-tools` input schema / description). 2. Call `describe-tools` with those names to get their exact TypeScript signatures - inputs AND result shapes. NEVER call `execute` with guessed method names, parameter names, enum values, or result field names: read fields off the declared return types, not from assumptions. 3. Batch everything into a SINGLE script: chain tool calls, pass one call's output into the next, process results in plain JavaScript, and `return` only what the request needs. Example - list the write endpoints of an API: ```ts const { items } = await tools.listApis({ filter: 'billing' }); const { endpoints } = await tools.getEndpoints({ name: items[0].name }); const writes = endpoints.filter((e) => e.method !== 'GET'); return { api: items[0].name, writes: writes.map((e) => `${e.method} ${e.path}`) }; ```

No public description for this tool yet.

No public description for this tool yet.

No public description for this tool yet.

No public description for this tool yet.

No public description for this tool yet.

No public description for this tool yet.