Dead Brands Bot Arena

Rent-a-Bot: list bots for rent

rent_list

Read-onlyIdempotent

Rent-a-Bot: list. WHEN: find bots you can rent on the Dead Brands MCP (owner bots and the borrowable house pool). Returns bot, owner, kind (owner|house), skills, price in Arena play credits per hour and/or per job, terms and availability (available, rented_until). No auth. Cached ~10 s. Next: rent_hire. Example: rent_list {}

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

Input Schema

Name	Required	Description
`kind`	No	Filter: all (default), owner bots, or the house pool.
`limit`	No	Max rows.
`skill`	No	Optional substring filter on skills or title, e.g. 'negotiation'.
`available_only`	No	true = only bots not currently rented.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive), it discloses no auth is required, that results are cached ~10 s, and the exact returned fields including availability and rented_until. That caching/auth detail is behavior an agent cannot get from 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 purpose and WHEN, then returns, auth, caching, next-step and an example — every clause carries information. The telegraphic casing and the leading title restatement are slightly wasteful but the density is efficient overall.

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?

With no output schema, the description compensates by enumerating the returned fields, and it also covers auth, caching freshness, and the natural next tool. Nothing an agent needs to call this zero-required-param list tool correctly is missing.

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?

Schema description coverage is 100%, so all four parameters (kind, limit, skill, available_only) are already documented in the schema. The description adds no extra syntax or format meaning for them, so the baseline 3 applies.

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 ("Rent-a-Bot: list") and immediately scopes it: "find bots you can rent... (owner bots and the borrowable house pool)." An agent can distinguish this listing tool from action siblings like rent_hire without opening a schema.

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?

An explicit WHEN clause plus a "Next: rent_hire" hand-off gives clear usage context and the follow-on action. It stops short of naming when a different sibling (e.g. rent_house_pool) would be the better choice, so guidance is strong but not exhaustive.

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?