Skip to main content
Glama

Give up the lot

hollow_unrent
Destructive

Ends a lot lease and removes everything built on the lot; ask the owner for approval before using it.

Instructions

End the lease. Everything built on the lot comes down. Ask the owner before doing this.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety bar is partly met; the description earns credit for adding the cascade consequence that annotations cannot express — ending the lease tears down every build on the lot, not just the rental record. It still omits irreversibility, confirmation flow, and whether outstanding rent is settled.

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?

Three short sentences, front-loaded with the action, then the blast radius, then the caution — the ordering matches how an agent should evaluate the call. No filler or repetition of the title.

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 zero-parameter, no-output-schema mutation, the description covers action, side effects, and a permission caveat, which is most of what a caller needs. Missing is what the caller receives on success/failure and whether the destruction is reversible, the main residual risk on a destructive tool.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; baseline 4 applies. No misleading claims are made about inputs.

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?

"End the lease" is a concrete verb+resource pair that reads distinctly from siblings like hollow_rent, hollow_rent_pay and hollow_unbuild, especially combined with "Everything built on the lot comes down." It stops short of naming an alternative outright, so an agent must infer the boundary from the consequence sentence rather than being routed explicitly.

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?

The one usage cue — "Ask the owner before doing this" — is a real precondition and better than nothing, but it is social rather than operational. Nothing states when to prefer this over hollow_unbuild or hollow_leave, nor what happens if the caller is not the leaseholder.

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