Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Find a clear region

find_clear_region
Read-only

Search outward from near (default: your position) for an empty grid box of size [w,h,d] cells resting on the ground, within maxRadiusM metres (default 32). Returns {found, aabb_grid:{min,max}, world_center, iterations}. Use BEFORE picking a build site to avoid trap-self / adjacency failures. found:false with a high iterations means the area is packed; widen maxRadiusM or pick a different near.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nearNoWorld [x,y,z] or {x,y,z} to search around (default: your position).
sizeYesBox size in cells [w,h,d], each 1..256.
spaceYes
maxRadiusMNoSearch 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.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, which are consistent with a search operation. The description adds behavioral context: it searches outward from a given point, finds a box resting on the ground, and returns specific fields. It also explains potential failure modes (trap-self/adjacency failures) and result interpretation.

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?

The description is concise (two sentences) and well-structured. It front-loads the core purpose, includes defaults, return fields, and usage advice in a compact form without unnecessary words. Every sentence adds value.

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 there is no output schema, the description adequately documents the return (found, aabb_grid, world_center, iterations) and provides guidance on interpreting results. It also covers the tool's context (searching for build site clearance) and edge cases (packed area). The description fully enables correct invocation and understanding.

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 75% of parameters with descriptions. The description adds meaningful defaults: near defaults to your position, maxRadiusM defaults to 32. It also explains the size parameter as [w,h,d] cells. The 'space' parameter is not elaborated in the description, but schema coverage is high so overall added value is good.

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's function: searching outward from a point for an empty grid box of specified size on the ground. It explicitly mentions the purpose ('find a clear region') and distinguishes it from sibling tools like survey_site by advising to use it before picking a build site to avoid failures.

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 gives explicit usage guidance: 'Use BEFORE picking a build site to avoid trap-self / adjacency failures.' It also provides advice on interpreting results ('found:false with a high iterations means the area is packed; widen maxRadiusM or pick a different near.'). While it doesn't explicitly state when not to use, the guidance is sufficient for effective use.

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