Skip to main content
Glama

Pay rent

hollow_rent_pay

Pays the current lease rent before the town collects it on the 1st; costs RC and works only when the owner enables ETHER_HOLLOW_SPEND.

Instructions

Pay what the lease owes now (the town otherwise takes rent on the 1st). Costs RC (100 RC = $1): refused until the owner starts the server with ETHER_HOLLOW_SPEND=1.

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

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?

Adds substantial behavior beyond the annotations: it costs RC with an explicit exchange rate (100 RC = $1), and critically, it is refused unless the server operator sets ETHER_HOLLOW_SPEND=1 — a hard runtime precondition an agent could never infer from readOnlyHint/openWorldHint. The non-idempotent annotation is reinforced by the per-call cost. It stops short of describing what state the lease/payment record ends in after success.

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 tight sentences, front-loaded with the action, followed by timing, cost, and the blocking precondition in that order of importance. The RC-to-dollar parenthetical earns its place by making the cost interpretable.

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 mutation tool with no output schema, the description covers the essentials an agent needs before calling: what it does, when it happens automatically, what it costs, and the refusal condition. It leaves the post-payment outcome (does the lease close, does an event get emitted) unstated, which is the main remaining gap.

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 semantics to explain and the baseline is 4. The description correctly implies the target lease is determined by context (the caller's own lease) rather than by an argument.

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 action and object: it pays the rent currently owed on a lease, and clarifies that payment is immediate ('now'). It implicitly distinguishes itself from the automatic collection on the 1st, though it does not name any sibling tool (e.g. hollow_rent) to sharpen the boundary.

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 parenthetical 'the town otherwise takes rent on the 1st' implies the use case is prepaying before auto-collection, which is real context. However, there is no explicit 'use this when...' framing, no statement about the preconditions (must hold a lease / owe rent), and no named alternative for merely inspecting rent owed.

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