Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Inspect a region (cell list)

inspect_region
Read-only

List the SOLID cells in a grid box. Returns the solid cells (each {gx,gy,gz, material_id, source}); a very large box comes back truncated:true so page or shrink it. Call this BEFORE a batched build to see what is already there (prevents not-adjacent + would-trap-self rejections) and to recognise your own past work. Grid→world: x=gx0.5, y=2.0+gy0.5, z=gz*0.5. material_id is null for procedural ground nobody placed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxYesMax grid corner [gx,gy,gz]. A very large box returns truncated:true (page or shrink).
minYesMin grid corner [gx,gy,gz].
spaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / max / items
      Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / max / maxItems
      Added value: +3
    • addedInput schema / properties / max / minItems
      Added value: +3
    • changedInput schema / properties / min / items
      Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / min / maxItems
      Added value: +3
    • addedInput schema / properties / min / minItems
      Added value: +3
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses truncation behavior (truncated:true), grid-to-world conversion formula, and that material_id is null for procedural ground. Annotations already declare readOnlyHint and openWorldHint, so this adds significant behavioral context beyond annotations without contradiction.

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?

Two sentences pack purpose, usage, behavioral details, and coordinate conversion without redundancy. Every sentence provides unique, valuable information.

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?

For a simple listing tool with no output schema, the description covers key aspects: result contents, truncation, coordinate mapping, and material meaning. Could mention that the result is an array, but that's implicit. Sufficient for correct use.

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

Parameters3/5

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

Schema coverage is 67%; max parameter has a brief description in schema, min and space less so. Description adds context about truncation related to max but does not elaborate on space or min. It adds some value but not complete compensation for the schema gaps.

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?

Description clearly states the tool lists SOLID cells in a grid box (verb+resource). It distinguishes from siblings like inspect_region_provenance and find_clear_region by focusing on the cell list and its specifics.

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?

Explicitly advises to call before a batched build to prevent rejections and to recognize past work. Also notes truncation and provides paging/shrinking advice. Could be stronger on when-not-to-use, but the guidance is clear and practical.

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