Skip to main content
Glama

Look around

look_around
Read-only

Snapshot of what is near you: your position (you.position in world floats AND you.grid in integer build cells, so you never hand-convert), nearby players (deduped - each person appears once), recent chat, recent nearby edits, a terrain block (terrain.ground_y = the surface to stand/build on; standing_on; nearby solid density; forward obstacle; terrain.looked_at_subject = the world coord of the thing you are looking at, which you should pass to append_memory as subjectPosition so an observation memory anchors to WHAT you saw, not where you stood), you.body (your own body status: grounded / embedded / blocked_dirs / headroom, so you can tell WHY you cannot move and fix it with move_to + place_block(op:"remove")), current_region (the named region you are currently standing inside, or null; its coverage field is 0..1 = how much of that region you have actually walked/observed so far, so check it before claiming "there is nothing here" or "this build is done" - low coverage means keep exploring), and memories_here (your OWN past memories anchored near where you stand: each {memory_id, kind, text, distance_m}, nearest-first - this is your spatial recall surfaced for free every look, occlusion-blind so you remember what happened HERE including behind a wall, without a separate call; act on them and pass their memory_id to mark_memories_used when one shapes what you do).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds extensive behavioral details: deduped players, occlusion-blind memories, terrain surface coordinates, body status linking to movement issues, region coverage interpretation, and memory anchoring usage. No contradiction with annotations.

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 front-loaded with the overall purpose and then breaks down each field with inline explanations. It is relatively long but each sentence adds value. Minor redundancy (e.g., repeating 'deduped') but overall efficient for the detail level.

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?

With one parameter and no output schema, the description thoroughly covers all output fields: position formats, player dedup, chat, edits, terrain coordinates, body status, region coverage semantics, and memory anchoring. It is sufficient for an agent to understand and use the tool correctly.

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

Parameters2/5

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

Schema coverage is 0%, and the description does not explain the required 'space' parameter. The purpose implies it is the space name, but this is not explicit. The description fails to compensate for the missing schema description.

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 provides a 'Snapshot of what is near you' and lists all the specific components (position, players, chat, edits, terrain, body, region, memories). The verb-resource combination is specific and distinct from siblings like 'look_at' and 'scan', though explicit differentiation is absent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool should be used regularly for spatial awareness ('your spatial recall surfaced for free every look'), but does not explicitly specify when to use it versus alternatives like 'look_at' or 'scan', nor provides any usage exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources