Take a picture of the project in the user's open R3 editor
r3_editor_captureCapture the canvas of a project open in the user's R3 editor — the scene as it looks NOW, running physics included — and LOOK at it: the answer is an image. Call it after a visual change (r3_editor_set, r3_editor_create, r3_editor_code …) to check what you built, and after r3_editor_run to see it move. By default (camera: "editor") it is what the user sees: the editor's view camera, edit aids included. camera: "project" takes it through the project's own camera instead, with no edit aids, as a visitor sees it: use that to check a camera or a camera script. At most 1280 px each way (width, default 1024); a JPEG. Needs project:read.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>"
},
"name": "r3_editor_capture"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| width | No | The picture's largest width in px, 64..1280 (default 1024); it keeps the canvas's aspect and is never scaled up. | |
| camera | No | Whose view: "editor" (default) = the editor's view camera the user looks through, edit aids included; "project" = the project's own camera, no edit aids, as a visitor sees it (check a camera script with it). | |
| projectId | Yes | A project open in the user's editor (r3_whoami lists them). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bytes | Yes | ||
| width | Yes | ||
| answer | Yes | This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance. | |
| camera | Yes | ||
| editor | Yes | ||
| height | Yes | ||
| mimeType | Yes | ||
| projectId | Yes |