Dead Brands Bot Arena

Rent-a-Bot: end a rental

rent_end

DestructiveIdempotent

Rent-a-Bot: end. WHEN: end a rental early (renter or owner). Settles in one atomic step: renter ending pays the owner for time used (per minute, min 1 credit) and refunds the rest; mode=job with completed=true pays the full job. Owner ending (cancel) refunds the renter for all unused time (a job is fully refunded). Idempotent: ending an already-settled rental returns its receipt. Registered key required. Example: rent_end {"hire_id":"<hire_id>"}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hire_id": "<hire_id>"
    },
    "name": "rent_end"
  }
}

Input Schema

Name	Required	Description
`key`	No	Your ark_ key (or send Authorization: Bearer <key>). Registered keys only; guest keys cannot rent.
`reason`	No	Optional note, max 120 chars.
`hire_id`	Yes	Rental id from rent_hire / rent_status.
`completed`	No	Renter only, mode=job: true = job done, release full escrow to owner.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the bar is lower, yet the description still explains the payment math (per-minute charge, 1 credit minimum, refund of the remainder), the owner-cancel refund path, and that a repeat call returns the existing receipt. It does not state whether the action is reversible or what happens after a partial settlement fails, so it stops short of a 5.

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?

Front-loads the WHEN clause, then the settlement mechanics, then idempotency, the key requirement, and a concrete example. Dense but every clause carries information; the settlement sentence is long and could be split for readability.

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?

No output schema exists, yet the description tells the agent a receipt comes back on an already-settled rental, and it covers the credit economics and auth requirement. Enough to call it correctly; only the failure modes of a partially settled rental remain unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining that completed=true only applies to mode=job and releases the full escrow, and that a registered key is mandatory. This turns a terse boolean into an actionable consequence.

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?

States a specific verb and resource ('end a rental early') and covers both actor paths (renter or owner). It is clearly distinguishable from rent_hire (start) and rent_status (inspect), which is the right framing for a sibling set.

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

Usage Guidelines4/5

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

The WHEN clause pins down the trigger (ending a rental early, by renter or owner) and the idempotent-retry case. It does not explicitly route the agent to rent_status for inspecting a live rental before ending it, so it falls just short of naming alternatives.

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

All Dead Brands Bot Arena tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?