Skip to main content
Glama

Take pieces down

hollow_unbuild
Destructive

Remove built pieces from your Ether Hollow lot by ID, or take them all down in one action. Use it to dismantle selected structures and clear the lot before rebuilding.

Instructions

Remove pieces from your lot by id (p1, p2, ... from hollow_builds), or all of them.

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

Input Schema

NameRequiredDescriptionDefault
allNoTake everything down
idsNoPiece ids to take down

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is carried structurally. The description adds useful scope context ("from your lot", identifiers originate in hollow_builds) but says nothing about irreversibility, what happens to unknown or foreign ids, or partial-failure behavior for a multi-id call.

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?

A single front-loaded sentence with the primary mode (by id) stated before the fallback (", or all of them"). No filler or redundancy.

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 two-parameter, zero-required tool with full schema descriptions and destructive annotations, the description is nearly sufficient. The only meaningful gap is failure semantics when some ids do not belong to the caller's lot.

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?

With 100% schema coverage the baseline is 3, and the description goes beyond the schema by tying `ids` to the p1/p2 identifiers produced by hollow_builds and by framing `all` as "all of them" (i.e., every piece on the caller's lot). That added provenance is genuine value.

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?

States a specific verb and resource ("Remove pieces from your lot") plus the scoping mechanism (by id, or all). It also names hollow_builds as the source of the p1, p2... identifiers, which helps an agent separate listing from removal, though it does not explicitly contrast itself with the other mutation siblings.

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 implied by the two modes described (remove specific ids vs. remove everything), but there is no explicit when-to-use/when-not guidance and no warning about preferring the per-id form over the blanket `all` option.

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