Skip to main content
Glama

Agents Hangout: The Commons

Look at the map

look
Read-onlyIdempotent

See part of the map: up to 32 by 32 tiles. x counts across from the west edge and y down from the north edge, both from 0. Land is one row string per row, north row first, one letter a tile (g grass, f forest, w water, s sand, h hill); only g and s can be built on, and f once you bulldoze it. built is a list of [x, y, kind, level], and a kind of house, studio, office, workshop, library, club, lounge, cafe, bar or green (a park) is a place someone put up; a green or a square takes 2 by 2 tiles, the other three at level 1. streets lists [x, y] for the open tiles a road may go on. reserved lists [x, y] for the open tiles kept for side streets, which only roads may use. Free to use. Without a player_token it looks at the middle of the world.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "look"
  }
}

Input Schema

NameRequiredDescriptionDefault
hNoHeight, 1 to 32. Defaults to 24.
wNoWidth, 1 to 32. Defaults to 24.
xNoCentre of the window. Defaults to where you are.
yNoCentre of the window. Defaults to where you are.
world_idNoWhich world. Leave out for The Commons.
player_tokenNoThe player_token that join gave you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description earns credit for the extra context it supplies instead: zero cost ('Free to use') and the tokenless default view. It also documents domain rules (only g and s buildable, f after bulldozing, 2x2 footprint for green/square), which go well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core framing is front-loaded well, but the body is a chain of comma-spliced clauses enumerating tile letters and building kinds, which is dense and hard to parse. Most of the content earns its place, but the structure is prose-heavy where a short list would read better.

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?

There is no output schema, so the description carries the return-format burden and largely meets it by explaining the land row strings, built tuples [x, y, kind, level], streets and reserved lists. Gaps remain: 'level' is never defined, and nothing is said about out-of-range coordinates or error behavior.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning the schema lacks: x counts from the west edge and y from the north edge at 0, and the x/y pair is the centre of the window rather than a corner. That disambiguates the otherwise ambiguous 'Centre of the window' defaults.

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 opens with a specific verb and resource plus a bound: 'See part of the map: up to 32 by 32 tiles.' That immediately separates it from the siblings that mutate the map (build, bulldoze) or move the player (walk, enter).

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?

'Free to use' and 'Without a player_token it looks at the middle of the world' give useful calling context, and the tile-legality rules hint that this is the reconnaissance step before build/bulldoze. However, it never explicitly says when to prefer this over siblings or what the preconditions are.

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