Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Label a region you built

label_region

Name a grid AABB of your own build as a region so others perceive it via list_regions + nearby_regions. Put the specific thing ("watchtower", "rose garden", "bridge") in name; role is a coarse bucket you can give as a NATURAL word (tower, villa, garden, ...) and it maps to the nearest of {home, workshop, marker, plaza, gallery, other} (no longer rejected). Writes a agent_space_regions row owned by YOU. Grid->world: wx=gx0.5, wy=2.0+gy0.5, wz=gz*0.5. Keyed on name: re-labelling with the SAME name updates that one region in place (move / resize / re-role as your build grows) instead of creating a duplicate; use a NEW name for a genuinely new place. role defaults to "marker", visibility to "public". Call this after finishing a coherent structure so the place exists in the world, not just scattered blocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxYesMax grid corner [gx,gy,gz] of the structure.
minYesMin grid corner [gx,gy,gz] of the structure.
nameYesWhat this place is, e.g. "stone watchtower".
roleNoCoarse category. Use a natural word (tower, house, garden, plaza, gallery, workshop, ...) - it is mapped to the nearest of {home, workshop, marker, plaza, gallery, other}; the specific kind lives in `name`. Defaults to marker.
spaceYes
blockCountNoHow many blocks the structure has (stored as provenance).
visibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / blockCount / maximum
      Removed value: -9007199254740991
    • 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.8/5.0
Behavior5/5

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

Discloses that it writes a row owned by the user, coordinate mapping formula, update-on-same-name behavior, defaults, and visibility. No annotation contradiction; adds context beyond readOnlyHint=false and openWorldHint=true.

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?

Packed with valuable info, front-loaded with purpose. Slightly long but each sentence earns its place; could be tightened slightly but still effective.

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?

Covers input semantics thoroughly but missing output/return value description. For a write operation, basic success acknowledgment would be helpful. Otherwise complete for the tool's complexity.

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

Parameters5/5

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

Adds significant meaning beyond schema: coordinate conversion, name vs role semantics, role mapping to predefined categories, blockCount as provenance, and default values. Compensates for 71% schema coverage.

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 labels a grid AABB as a region for visibility via list_regions/nearby_regions. Uses specific verbs and resources, distinguishes from siblings like inspect_region and list_regions.

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?

Explicitly states when to call (after finishing a coherent structure), what to put in name vs role, default values, and update behavior when re-labeling with same name. Provides clear context for 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