Token Budgets

Large Godot scenes can have hundreds of nodes. A fully detailed snapshot of a 200-node scene would easily exceed 50,000 tokens — blowing up your context window and making the response useless. Theatre manages this problem through token budgets and detail levels.

The problem

When you call spatial_snapshot, the server has to decide how much data to include. More data means:

• More tokens consumed from your context window
• Slower response time
• More noise for the agent to filter through
• Higher cost per tool call

Less data means the agent might miss relevant nodes.

Theatre solves this with a budget-first design: every data-returning tool accepts a token_budget parameter and a detail level. The server measures the response as it builds it and stops adding data once the budget is reached. The most relevant data is always included first.

Detail levels

The detail parameter controls how much information is included per node.

standard (default)

Returns position, velocity, rotation, scale, and common flags (approximately 150-250 tokens per node). This is the default detail level — a good middle ground that gives orientation plus basic properties without noise.

summary

Returns only the essential spatial information for each node:

{
  "Player": {
    "class": "CharacterBody3D",
    "global_position": [2.3, 0.0, -1.7],
    "velocity": [0.0, -2.4, 0.0]
  }
}

This is roughly 80-120 tokens per node. Good for answering "where is everything?" questions when you do not need property details.

full

Returns all tracked properties:

{
  "Player": {
    "class": "CharacterBody3D",
    "global_position": [2.3, 0.0, -1.7],
    "rotation_deg": [0.0, 45.2, 0.0],
    "velocity": [0.0, -2.4, 0.0],
    "scale": [1.0, 1.0, 1.0],
    "visible": true,
    "collision_layer": 1,
    "collision_mask": 3,
    "on_floor": false,
    "on_wall": false
  }
}

This is roughly 300-500 tokens per node. Good when you need the complete picture for a specific set of nodes.

The token_budget parameter

Every snapshot-style tool accepts token_budget (integer). The default varies by detail tier: summary defaults to 500, standard to 1500, and full to 3000.

{
  "detail": "summary",
  "token_budget": 500
}

The server builds the response node by node, measuring token usage as it goes. When adding the next node would exceed token_budget, it stops and includes a truncated: true flag in the response:

{
  "frame": 412,
  "node_count": 200,
  "included_nodes": 12,
  "truncated": true,
  "nodes": { ... 12 nodes ... }
}

The node_count tells the agent how many nodes exist; included_nodes tells it how many were included. If the response is truncated, the agent knows to narrow its query.

Priority ordering

When the budget forces truncation, which nodes are included first?

If focal_node is set: The focal node is always included first, then nodes are included in ascending order of distance from the focal node.

If class_filter is set: Nodes matching those types are included first, then others.

Otherwise: Nodes are included in scene tree order (breadth-first from root).

This means token_budget: 500 with focal_node: "Player" gives you the player plus the nearest nodes, not the first 5 nodes in the tree (which are often UI elements or root containers).

Practical budget guidelines

Scenario	Recommended settings
"Where is everything?" overview	detail: "standard", token_budget: 1500 (tier default)
Focus on one area of the scene	detail: "summary", focal_node: "Player", token_budget: 500
Debug a specific node	Use spatial_inspect instead of snapshot
Monitor changes over time	Use spatial_delta — only changed nodes included
Check scene structure (no spatial data)	Use scene_tree — very compact
Small scene (< 20 nodes)	detail: "full", token_budget: 3000 (tier default)

spatial_delta as the budget-friendly choice

When the game is running and you want to know what changed since the last snapshot, use spatial_delta instead of spatial_snapshot. Delta computes changes against the baseline established by the most recent spatial_snapshot call — there is no since_frame parameter. Delta responses only include nodes whose tracked properties changed since that baseline:

{
  "frame": 450,
  "baseline_frame": 400,
  "elapsed_ms": 833,
  "changed_node_count": 1,
  "nodes": {
    "Player": {
      "global_position": [3.1, 0.0, -2.3],
      "velocity": [2.0, 0.0, 0.0]
    }
  }
}

If only the player moved, the delta omits unchanged nodes. The exact response-size reduction depends on the scene and selected properties.

spatial_inspect for single nodes

When you need full detail on exactly one node, spatial_inspect is more efficient than a full snapshot:

{
  "node": "EnemyDetectionZone",
  "include": ["transform", "physics", "spatial_context"]
}

This returns the selected tracked categories for one node plus its requested spatial context. It narrows the response, but the normal response budget still applies.

Recording budget behavior

The clips tool's query_range action has its own budget parameter (max_frames). When querying a large frame range, use:

{
  "action": "query_range",
  "clip_id": "clip_01",
  "from_frame": 300,
  "to_frame": 325,
  "nodes": ["Player", "Enemy"],
  "detail": "summary"
}

Specifying nodes limits data to only those nodes across all frames. detail: summary keeps per-frame data compact.

Capping the maximum budget

If you want to enforce a server-side ceiling on response size regardless of what the caller requests, use token_hard_cap in spatial_config:

{
  "token_hard_cap": 4000
}

This hard cap persists for the duration of the server session. Individual tool calls can still request smaller budgets, but they cannot exceed the cap. Useful when you want to protect your context window across a long session.