Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Declare a build goal

set_goal

Declare what you intend to build in this space. Persists across brain resets. Any prior active goal is automatically superseded; if it had >= 5 blocks placed, a region is auto-created from its accumulated footprint before being closed. Returns {ok, goalId}. Call this ONCE when you start a new structure, before placing any blocks. Optionally pass plan_build output (target_blocks, footprint, height) to persist the plan target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYes
heightNoPlanned height in cells from plan_build.
footprintNo[w, d] footprint in cells from plan_build.
descriptionYesWhat you plan to build, e.g. "a stone tower with stairs". This becomes the region name if auto-created.
target_blocksNoTotal planned blocks from plan_build.target_blocks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / footprint / items
      Previous value: -[
-  {
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / footprint / maxItems
      Added value: +2
    • addedInput schema / properties / footprint / minItems
      Added value: +2
    • removedInput schema / properties / height / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / target_blocks / maximum
      Removed value: -9007199254740991
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses important behavioral traits: persistence across resets, auto-supersede of prior goal, auto-region creation condition (>=5 blocks), and return format. Annotations (readOnlyHint=false, openWorldHint=false) are consistent, and the description adds context beyond them.

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

Conciseness5/5

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

Four sentences, each adding essential information. No redundant text. Front-loaded with main purpose, then details. Efficient and well-structured.

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

Completeness4/5

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

The description covers behavior, return, and parameter guidance adequately for a 5-parameter tool with no output schema. It could mention what happens if <5 blocks, but the agent can infer from the condition. Overall complete.

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?

The schema covers 80% of parameters with descriptions. The description adds value by linking optional parameters (target_blocks, footprint, height) to plan_build output and explaining that 'description' becomes the region name if auto-created. This clarifies usage 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 the tool declares a build intention, with specifics like persisting across resets and auto-creating regions. It distinguishes from siblings like plan_build and complete_goal by specifying when to call it (once at start, before placing blocks).

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

Usage Guidelines4/5

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

The description explicitly says to call it once before placing blocks and optionally pass plan_build output. However, it does not explicitly state when not to use it or list alternatives, though the context with sibling tools makes it clear.

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

All space0 toolsInspect
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