Skip to main content
Glama

cpu_demolish

Remove a building from a Land cell you own to clear it for a different structure. Requires an active session and costs a fraction of the build cost in $CPU plus build materials; the cell must not have active mining or crafting.

Instructions

Remove the building from a Land cell you own, clearing it for a different building. Requires a session — call cpu_authenticate first. Not free: it burns a fraction of the building’s build cost in $CPU (auto-approved) and consumes some of its build materials from the cell’s warehouse (no refund) — see each building's demolishCost in cpu_get_game_config for the exact amounts. The cell must have no active mining or craft process — a craft frees its slot once fully claimed, but a mining run only ends when its deposit is exhausted, so a mining extractor cannot be demolished mid-run; a hub can only be demolished when it is not mid-route or anchoring open trade lots. Deposits and other warehouse balances are preserved. Afterward the plot is locked from rebuilding for the building's build time (its demolishFinishAt); cpu_get_cell/cpu_get_attention surface the cooldown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenIdYesThe tokenId of a cell you own whose building to remove.
Behavior5/5

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

Given no annotations, the description fully discloses behavioral traits: it consumes resources (CPU and materials), preserves deposits and warehouse balances, and imposes a cooldown. It also explains restrictions and references other tools for exact costs.

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?

The description is well-structured and front-loaded with the main purpose. While slightly verbose, every sentence contributes necessary context. It balances detail with clarity.

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

Completeness5/5

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

The description is comprehensive, covering prerequisites, costs, restrictions, and outcomes. No output schema exists, but the description adequately explains what the tool does without needing to detail return values.

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?

The only parameter, tokenId, is described identically in both the schema and the description. With 100% schema coverage, the description adds no additional meaning beyond what the schema already provides, warranting a baseline score of 3.

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 clearly states the action: 'Remove the building from a Land cell you own, clearing it for a different building.' This is a specific verb+resource combination, and it effectively distinguishes the tool from siblings like cpu_build or cpu_buy_lot.

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

Usage Guidelines5/5

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

The description explicitly provides prerequisites ('Requires a session — call cpu_authenticate first'), costs, and conditions for use (no active mining or craft process, specific rules for mining extractor and hub). It also references alternatives like cpu_get_game_config for details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sodiqit/project-cpu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server