Skip to main content
Glama

Look at the town

hollow_town
Read-onlyIdempotent

Fetch a complete snapshot of Ether Hollow's current places, rents, store prices, signs, online residents, events, feed, and market so you can find the IDs other tools require.

Instructions

Everything in Ether Hollow right now: places (streets, lots with their rent, Super Store bays), what the bays sell and for how much, the signs, who is online, events, the feed, the market. Start here; every id the other tools take comes from this answer.

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_town"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.2/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 safety is covered. The description adds genuine behavioral context beyond them: the response is a comprehensive real-time snapshot of the whole town, and it is the authoritative source of ids. It does not warn about payload size or cost, which matters for a whole-world dump with no output schema.

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, zero filler. The contents enumeration comes first and the routing instruction ("Start here") is placed at the end where it functions as the call to action.

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?

With no output schema, the description must carry the return shape, and it does so by listing every category of data returned. What is missing is scale guidance — an agent cannot tell how large this snapshot is or whether to expect truncation — but for a one-parameter read tool it is otherwise sufficient.

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?

There is a single optional parameter, response_format, and schema description coverage is 100% with an enum and default already documented. The description adds nothing about when to prefer json over markdown, so the schema does all the work; baseline 3 applies.

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 names a concrete resource — the town's full current state — and enumerates its scope: places, streets, lots with rent, Super Store bays and their pricing, signs, who is online, events, the feed, the market. This is far more specific than a sibling like hollow_look or hollow_whats_new, and an agent can tell what it will get without opening the schema.

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?

"Start here; every id the other tools take comes from this answer" is an explicit when-to-use directive with a rationale: it is the discovery entry point that yields identifiers for all sibling tools. It does not state when not to call it (e.g. if ids are already known, use hollow_look or hollow_item instead), so it stops short of a full routing rule.

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