space0

Plan a build (block counts + scale refs)

plan_build

Read-only

Pure compute over your declared parts: sums block counts, returns a parts checklist, and attaches scale references so you can judge your design before placing a single block. You declare the parts; this computes block counts + scale references. It does not invent geometry. Workflow: call plan_build first to get target_blocks + scale_refs, then call set_goal(description, target_blocks, footprint, height) to persist the plan — set_goal is where plan metadata is stored. Returns { target_blocks, parts_checklist, scale_refs, overlap_warning? }. goal_id is accepted but is a no-op in this tool; persistence happens via set_goal.

Input Schema

TableJSON Schema

Name	Required	Description
`parts`	Yes	Declared parts. Each part has a name, role, and relative AABB. You declare ALL parts; plan_build only computes counts.
`space`	Yes
`style`	No	Optional architectural style hint (for get_material_palette style lookup).
`height`	Yes	Overall height in grid cells.
`goal_id`	No	Accepted for forward-compatibility but currently a no-op. To persist plan metadata, pass target_blocks/footprint/height to set_goal instead.
`subject`	Yes	What you plan to build, e.g. "a Korean palace gatehouse".
`footprint`	Yes	[w, d] overall footprint in grid cells.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedJun 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / footprint / maxItems
```
Added value: +2
```
addedInput schema / properties / footprint / minItems
```
Added value: +2
```
removedInput schema / properties / goal_id / maximum
```
Removed value: -9007199254740991
```
addedInput schema / properties / parts / items / additionalProperties
```
Added value: +false
```

changedInput schema / properties / parts / items / properties / aabb / description

Previous value: -"[minGx, minGy, minGz, maxGx, maxGy, maxGz] relative to the build origin."New value: +"[minGx, minGy, minGz, maxGx, maxGy, maxGz] relative to the build origin (bounded to +/-1,000,000 per axis)."

changedInput schema / properties / parts / items / properties / aabb / items

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  },
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  },
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  },
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  },
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  },
+  {
+    "maximum": 1000000,
+    "minimum": -1000000,
+    "type": "integer"
+  }
+]

addedInput schema / properties / parts / items / properties / aabb / maxItems
```
Added value: +6
```
addedInput schema / properties / parts / items / properties / aabb / minItems
```
Added value: +6
```

changedInput schema / properties / parts / items / properties / material / anyOf

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "maxLength": 64,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "maxLength": 64,
+    "minLength": 1,
+    "type": "string"
+  }
+]

First observedJun 4, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description aligns with readOnlyHint (pure compute) and openWorldHint (false) – no contradiction. Adds context about no-op nature of goal_id and that it does not persist data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Clear and front-loaded with key info, but could be slightly more structured (e.g., bullet points for return fields). Still efficiently conveys essential details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no output schema, and tool complexity, the description adequately covers workflow, return fields (target_blocks, parts_checklist, scale_refs, overlap_warning?), and behavioral caveats.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (86%) with good descriptions for most params. The description adds context about the parts parameter (you declare all parts) and the goal_id no-op, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a pure compute tool that sums block counts, returns a parts checklist, and attaches scale references. It explicitly distinguishes its role from siblings like set_goal, which handles persistence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit workflow: call plan_build first to get target_blocks + scale_refs, then call set_goal to persist. Also mentions what it does not do (invent geometry) and that goal_id is a no-op.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All space0 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?