Skip to main content
Glama

Look around

hollow_look
Read-onlyIdempotent

Inspect any place in the town to see who is standing there, what is built, and which signs are present; defaults to the resident's current location.

Instructions

What is at a place: who stands there, what is built, the signs. Defaults to where the resident stands.

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": "hollow_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoA place id from hollow_town; default where you stand
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds value beyond that by stating the scope of the observation (people, built structures, signs) and the default target location. It does not discuss any limits or how much of a place is returned, which keeps it short of a 5.

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, no filler: the first defines what is returned, the second defines the default target. The most decision-relevant information (what you get, and that you can call it with nothing) is front-loaded.

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 read-only, zero-required-parameter observation tool with a fully described schema and no output schema, the definition covers purpose, default behavior and content scope adequately. The only mild gap is that it does not sketch the shape of the answer, though response_format in the schema signals markdown vs structured JSON.

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 100%, with both parameters fully documented including the enum for response_format and the maxLength on 'at', so the schema carries the weight. The description's 'Defaults to where the resident stands' reinforces the optionality of 'at' but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (look/what is at) and resource (a place), then enumerates the returned content: who stands there, what is built, the signs. That is far more concrete than the bare name 'hollow_look' and distinguishes it from mutation siblings like hollow_build or hollow_move, though it never names a sibling to contrast against.

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?

Usage is only implied: 'Defaults to where the resident stands' tells the agent it can call with no arguments for the current location, and 'A place id from hollow_town' hints at the sourcing workflow. There is no explicit when-to-use versus when-not, and no contrast with nearby read tools such as hollow_here or hollow_read_sign.

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