Assistant tools
The guide assistant can request these actions from speech, chat, or quick-topic prompts.
| Tool | Purpose | Example request |
|---|---|---|
setCamera | Select an anchor asset or orient by latitude, longitude, and roll. | “Show Mars.” |
getNode | Retrieve a node and its dataset metadata by id. | “Read the current map's source from its metadata.” |
setNode | Change visibility; enables/disables overlays or shows a base map. | “Show country borders.” |
getLastTouchPoint | Retrieve the last touched latitude/longitude, if registered. | Touch the globe, then ask “Where did I touch?” |
setMarker | Place/update a pin without moving the camera. | “Mark Stockholm and keep this view.” |
clearMarker | Remove by ID/label, or omit ID to clear all markers. | “Remove the Stockholm marker.” |
setTime | Generic simulation-time action; not implemented in Webrender. | Time-change requests fail here. |
no-op | Internal action that lets the user continue. | No operator action needed. |
Asset selection and metadata
Tools use the ID in asset.json, not its title or path. For example, blue_marble selects earth/blue_marble/asset.json.
setCamera returns the selected node. getNode explicitly retrieves it again; the tested profile requests that check for every dataset.
Use setNode visibility to toggle overlays on a compatible Earth base. It can also show a base map, as in the recorded metadata test.
Marker example
setMarker requires an ID and coordinates; label, color, and size are optional:
{
"id": "stockholm",
"latitude": 59.33,
"longitude": 18.07,
"label": "Stockholm",
"color": "#ff3355",
"size": 1
}
Reuse the ID to update the marker. Size 1 is standard, 0.5 is half, and 2 is double. Camera movement is a separate action.
clearMarker matches an ID or a case-insensitive label substring. If several labels match, give the exact ID. Omit the ID to clear all markers. Direct controls are in Webrender → Markers.
Limits in the current renderer
Latitude, longitude, and roll work; altitude/zoom, simulation time, and timed camera journeys do not. The generic schema's duration parameter is in seconds but is not used to animate travel in Webrender.
Configure dataset transitions separately in Transitions. Video playback does not imply support for setTime.
Check that an action really happened
Expand a Tool Call entry in chat to inspect Arguments and Result. Confirm the dataset/overlay/marker in the globe preview or Webrender panel; a spoken claim alone is insufficient.
If an action fails, check Dashboard → Logs, the selected scene service, and the asset ID. Try an explicit request such as “Load asset blue_marble using setCamera.” Keep missing-metadata handling in your profile rules.