Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Survey a build site

survey_site
Read-only

Survey the ground before you build, in ONE call (instead of fanning out look_around + list_regions + find_clear_region + scan, which is slower and heavier). Returns { me (position + grid + body + facing), ground (ground_y to build on), neighbors (every named region nearby = existing structures you must NOT overlap or destroy - fit AROUND them), current_region, clear_footprint (a free ground box of the size you asked for, where you can safely build) and a plan_hint }. Workflow like a human builder: 1) survey_site to read the site, 2) DECIDE a FORM (footprint + height + the parts: foundation, walls with door/window openings, roof) and pick MATERIALS by colour via get_material_palette, 3) emit those parts as build ops in ONE build call (it auto-walks between reach bands so a tall structure finishes in one go). Pass size:[w,h,d] (cells) to also reserve a clear footprint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nearNoWorld [x,y,z] to survey around (default: your position).
sizeNoFootprint to reserve as a clear build box [w,h,d] cells. Omit to skip the clear-footprint search.
spaceYes
maxRadiusMNoClear-footprint search radius in metres (default 32).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / near / anyOf
      Previous value: -[
-  {
-    "items": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "number"
-      },
-      {
-        "type": "number"
-      }
-    ],
-    "type": "array"
-  },
-  {
-    "properties": {
-      "x": {
-        "type": "number"
-      },
-      "y": {
-        "type": "number"
-      },
-      "z": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "x",
-      "y",
-      "z"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "items": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "number"
+      }
+    ],
+    "maxItems": 3,
+    "minItems": 3,
+    "type": "array"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      },
+      "z": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "x",
+      "y",
+      "z"
+    ],
+    "type": "object"
+  }
+]
    • addedInput schema / properties / size / maxItems
      Added value: +3
    • addedInput schema / properties / size / minItems
      Added value: +3
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses that the tool is a read-only survey (consistent with readOnlyHint annotation) and returns comprehensive site data. It does not contradict annotations. However, it could mention that it does not modify the world, but the annotation already covers that.

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?

The description is clear and front-loaded with purpose, but it is somewhat long with workflow details. It could be slightly more concise without losing essential information.

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 no output schema, the description fully enumerates the expected return fields (me, ground, neighbors, etc.) and provides a workflow sequence. It covers all necessary context for an agent to invoke the tool appropriately.

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 description explains the 'size' parameter's role in reserving a clear footprint and notes it can be omitted. However, the 'space' parameter is not explained (schema also lacks description). The description adds context beyond the schema for some parameters but not all.

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 surveys a build site, distinguishes it from slower alternatives (look_around + list_regions + find_clear_region + scan), and lists the returned data (me, ground, neighbors, etc.).

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?

The description explicitly tells when to use the tool ('Survey the ground before you build') and contrasts with slower, heavier alternatives. It also provides a step-by-step workflow (1 survey, 2 decide form/materials, 3 build), guiding the agent on how to use the tool in sequence.

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