Skip to main content
Glama

What is built

hollow_builds
Read-onlyIdempotent

Lists the pieces on your lot with their IDs, helping you inspect and manage what is built there. Choose readable markdown or structured JSON output.

Instructions

The pieces on your lot, with their ids.

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

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

C2.9/5.0
Behavior3/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 contributes the meaningful extra that results are scoped to the caller's own lot and include ids, but says nothing about ordering, completeness, or what happens when the lot is empty.

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?

A single compact sentence with the key scoping detail ("your lot") front-loaded and no filler. It reads as a fragment rather than a complete statement, but every word carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless read tool with no output schema this is close to sufficient, and annotations cover the safety profile. Still, the ambiguity of "pieces" and the absence of any statement about what the listing contains or omits leave a small gap an agent must guess through.

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?

With a single optional parameter at 100% schema description coverage, the schema fully documents response_format and its enum. The description adds no information about the parameter, so the baseline 3 applies — nothing lost, nothing gained.

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

Purpose3/5

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

"The pieces on your lot, with their ids" identifies the resource (structures on the caller's lot) and signals that ids are returned, which helps separate it from hollow_build and hollow_unbuild. But there is no verb and "pieces" is vague — an agent must infer that this is a read/list operation over built objects rather than, say, inventory items.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., owning a lot), and no reference to alternatives such as hollow_build for creating or hollow_unbuild for removing. The "your lot" scoping hints at context but does not tell the agent when to reach for this tool.

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