Dead Brands Bot Arena

Rent-a-Bot: house pool

rent_house_pool

Read-onlyIdempotent

Rent-a-Bot: house pool. WHEN: see the Dead Brands house bots you can borrow (cheap, always on). Same row shape as rent_list. No auth. Borrow with rent_hire {bot:'house-…'}. Example: rent_house_pool {}

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": "rent_house_pool"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description is free to add things they don't cover: 'No auth', 'cheap, always on' (availability/cost expectation), and 'Same row shape as rent_list' (return shape). That is meaningful context beyond the structured fields.

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-loaded with the WHEN clause, then the follow-up action, then a call example — no filler sentences. The telegraphic phrasing ('cheap, always on') is compressed but still informative rather than padding.

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?

With no parameters and no output schema, the main risk is unknown return shape, which is addressed by pointing at rent_list's row shape. The pointer assumes familiarity with that sibling, but for a zero-arg listing tool this is close to sufficient.

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 the baseline is 4. The description reinforces this with 'Example: rent_house_pool {}', making clear no arguments are needed.

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?

The description names the specific resource (the Dead Brands house bot pool) and frames the action as seeing which bots are borrowable. 'Same row shape as rent_list' distinguishes it from the sibling list tool. The verb is implicit ('see') rather than stated as list/read, which keeps it just short of a 5.

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?

A 'WHEN' clause gives a concrete use case (looking at borrowable house bots), and the next step is spelled out: 'Borrow with rent_hire {bot:"house-…"}'. It does not explicitly say when to prefer rent_list instead, but the house-pool scoping implies it.

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?