See what is in an R3 project
r3_project_loadList the components in an existing R3 project — what it contains and, for each one, its entityRef: the name code addresses it by (this['mesh_cube_1']). Read this before writing any code for a project, and after any tool call whose outcome was reported as unknown, to see what actually landed. Value components (Vector3, Color, Scalar) are not listed individually — reach them through their owner, e.g. mesh.position.x. Each object says which entity it belongs to (entity: {entityRef, id}, or null; r3_component_set {"entity": …} changes it), and an entityRef several components share (the same name in different entities) is listed with their ids: tools refuse that name, use the id.
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_project_load"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | The project to read, from r3_project_create or the R3 app. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | 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. | |
| objects | Yes | ||
| projectId | Yes | ||
| componentCount | Yes | ||
| valueComponentCount | Yes |