Skip to main content
The canonical ngram_entity integration registers 23 spatial tools. A connected Spatial session can receive actions from another conversation with the same Entity. A messaging conversation does not create a Spatial session by itself. Blender authoring can run on the execution host before a surface connects. This reference follows the shipped Python schemas. Download the machine-readable definitions.
A tool can queue an action before the surface renders it. Optional capture, media, or motion features still depend on the connected browser and configured backend. See capabilities.

Creations and Blender

ar_world

Create, inspect, edit, and program a persistent creation world. The result comes from the connected surface. Call capabilities for the detailed world and JavaScript contracts. Approach returns an accepted task; use the correlated perform.completed or perform.cancelled event to establish its outcome. Observe important results once rather than repeatedly polling with model calls. See Creations and Programs for complete examples and human interaction controls.

ar_blender

Author a persistent headless Blender project on the configured execution host and publish GLB previews into Spatial. position is an initial Spatial placement in metres. Subsequent revisions preserve human transforms. execute can call publish() several times during one script; progress delivery does not require further model calls. Read Blender for installation, persistence, cancellation, and export limits.

Movement and expression

Request movement in the connected scene. An accepted action is not proof of completed movement; inspect its outcome when needed.
queue a physical gesture (wave, nod, point, dance, …).
queue a bodily emotional expression.
queue gaze toward the user or away.
return to a relaxed idle stance.No parameters.
speak mid-turn (visible + TTS) before your final reply. Use for reactions while reasoning; final answer can still go in normal reply text.

Panels and media

show a readable spatial panel for substantial information.
close a spatial panel by id.
write a concise status or result to the spatial terminal.
open an HTTP(S) page on the spatial browser surface.
play a specific YouTube video in the dedicated media player. On desktop this opens the desktop player; in immersive AR the surface uses its headset-safe playback flow. Search for a specific video first when needed.

Objects and environment

spawn a real 3D geometric primitive. Use for requests naming a shape such as cube, sphere, cylinder, cone, torus, or plane. Physics defaults on. Do not use ar_spawn_text as a substitute for geometry.
spawn an interactive physics toy. Use this for balls, bouncy balls, beach balls, dice, and marbles; use ar_spawn_object for generic geometry.
place visible lettering in the scene. Use only when the user asks for text or a label; never use it to represent a requested physical object or shape.
remove one previously spawned object, toy, text, image, or model by id.
clear all spawned scene objects when the user asks to reset or clean the space.No parameters.
place a labeled callout at scene coordinates.
change the shell’s environment preset.

Inspection and optional backends

inspect the current embodied surface contract, live context, and available spatial API tools. Use this instead of scanning workspace files when asked what the spatial body can do.No parameters.
ask the user-controlled surface for a current view image.
request a novel humanoid motion from the configured external GPU provider. Use only when generated motion adds clear value.

Design for the current surface

Use primitives for geometry and text tools for lettering. Use ar_spawn_toy for prepared physics objects, and ar_play_youtube for a specific video rather than opening a YouTube search page in the browser panel. ar_terminal displays text; it does not execute a shell command. ar_request_capture requests a rendered surface frame; it does not establish access to passthrough cameras. ar_generate_motion needs a configured external motion provider.