Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Look at one player or coordinate (focused, symbolic)

look_at

Higher-detail STRUCTURED view of one specific peer or coordinate (no pixels - the relay is renderer-less). For a peer: their position, distance, heading_from_you, recent chat lines from them. For a coordinate: tighter ground / standing-on / density / forward-obstacle probe than look_around at that one spot. Call this when you want to attend to one thing; otherwise use look_around for the broad view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYesSpace slug you are embodied in.
targetYesDiscriminated union on `kind`: {kind:"player", player_id:"<from who_is_here>"} OR {kind:"coord", position:[x,y,z] or {x,y,z}}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / target / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "kind": {
-        "const": "player",
-        "type": "string"
-      },
-      "player_id": {
-        "description": "Peer or other agent's player id (from who_is_here).",
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "player_id"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "kind": {
-        "const": "coord",
-        "type": "string"
-      },
-      "position": {
-        "anyOf": [
-          {
-            "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"
-          }
-        ],
-        "description": "World [x, y, z] or {x, y, z} you want a tighter look at."
-      }
-    },
-    "required": [
-      "kind",
-      "position"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "player",
+        "type": "string"
+      },
+      "player_id": {
+        "description": "Peer or other agent's player id (from who_is_here).",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "player_id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "coord",
+        "type": "string"
+      },
+      "position": {
+        "anyOf": [
+          {
+            "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"
+          }
+        ],
+        "description": "World [x, y, z] or {x, y, z} you want a tighter look at."
+      }
+    },
+    "required": [
+      "kind",
+      "position"
+    ],
+    "type": "object"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The description states the output is structured and non-pixel-based ('no pixels - the relay is renderer-less'), which is useful. However, the annotations indicate readOnlyHint=false, suggesting possible side effects, while the description implies a read-only query. There is no mention of side effects, permissions, or any behavioral nuances beyond the output, leaving a gap in transparency for a tool that may not be strictly read-only.

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 two sentences, front-loading the key purpose and scope, then detailing outputs for each target type. Every sentence adds necessary information, and the structure is efficient and clear.

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 provides a good overview of what the tool returns for both target types, covering position, distance, heading, chat lines for peers and ground, density, obstacle for coordinates. Given there is no output schema, this explanation is sufficient. It also mentions the sibling tool for context. However, it does not mention pagination or limits on returned data, which could be relevant for agents.

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 input schema already has 100% description coverage for both parameters. The description adds value by explaining the discriminated union for 'target' (player vs coord), clarifying that player_id comes from 'who_is_here', and describing the coordinate format. This goes beyond the schema by providing usage context and source for the player_id.

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 it is a 'Higher-detail STRUCTURED view of one specific peer or coordinate' and distinguishes from the sibling 'look_around' by specifying when to use each. The verb 'look at' plus the specific targets (peer or coordinate) make the purpose unambiguous.

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 advises 'Call this when you want to attend to one thing; otherwise use look_around for the broad view,' giving direct usage context and differentiating from the sibling. It also describes what information is returned for each target type, aiding in decision-making. It could be improved by stating when not to use it, but the contrast with look_around is strong.

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