Dead Brands Bot Arena

Rent-a-Bot: put your hired bot to work

rent_dispatch

Rent-a-Bot: dispatch. WHEN: you already hired a bot with rent_hire and want it to actually do the job. Pass hire_id plus game (the rented bot joins and plays that game as itself — the seat shows the house bot with your nickname) and/or brief (get a plan/answer). Only the renter, only while the rental is active. House bots keep their usual ~55-60% outside-player win balance; renting gives no win-rate edge. Rate-limited. No new charge. Registered key required. Next after a game dispatch: arena_get_state {match_id}. Example: rent_dispatch {"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_dispatch"
  }
}

Input Schema

Name	Required	Description
`key`	No	Your ark_ key (or send Authorization: Bearer <key>). Registered keys only; guest keys cannot rent.
`game`	No	Live game id for the rented bot to play, e.g. laser_dash.
`brief`	No	Optional job brief or follow-up, max 500 chars. If omitted, the hire brief is answered.
`hire_id`	Yes	Rental id from rent_hire / rent_status.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare non-readOnly, non-idempotent, non-destructive, but say nothing about cost, auth, rate limits, or fairness. The description adds all of these: 'No new charge', 'Rate-limited', 'Registered key required', renter-only while active, and discloses that renting gives no win-rate edge because house bots hold ~55-60%. That is exactly the kind of non-obvious behavior an agent needs.

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 a WHEN clause and a concrete call example at the end, with little wasted text. It is dense with parentheticals and multiple clauses per sentence, which slightly hurts scannability, but every sentence carries actionable information.

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?

For a non-read-only, non-idempotent action tool with no output schema, the description covers auth requirements, cost, rate limiting, eligibility, the two dispatch modes, and the exact next call. Nothing material an agent needs before invoking is missing.

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; the description earns more by explaining what `game` and `brief` actually cause ('the rented bot joins and plays that game as itself — the seat shows the house bot with your nickname', 'get a plan/answer'), plus the default that omitting brief answers the hire brief.

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?

Specific verb+resource: dispatching an already-hired bot. The description states the precondition ('you already hired a bot with rent_hire') and what happens ('the rented bot joins and plays that game as itself'), which clearly separates it from rent_hire, rent_status, and arena_act.

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

Usage Guidelines5/5

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

Explicit WHEN section names the triggering condition, and the two dispatch modes (game vs. brief) are laid out with an 'and/or' rule. It also names the required follow-up tool: arena_get_state {match_id} after a game dispatch.

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?