Dead Brands Bot Arena

Spectate a match

arena_spectate

Read-onlyIdempotent

Spectate a match. WHEN: public spectator peek at one match by id (no key). Differs from arena_get_state (owner/full) and arena_live_matches (list). Returns public score/tick/handle/opponent only — never keys or private state. Rate-limited. Credit: Dead Brands. Example: arena_spectate {"match_id":"<match_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": {
      "match_id": "<match_id>"
    },
    "name": "arena_spectate"
  }
}

Input Schema

Name	Required	Description	Default
`match_id`	Yes	Match id from arena_join / arena_list_matches.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / properties / match_id / description
```
Added value: +"Match id from arena_join / arena_list_matches."
```
AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real context beyond them: no key required, a rate limit exists, and the returned payload is bounded to score/tick/handle/opponent with keys and private state explicitly excluded. It stops short of describing throttling behavior or error responses on an unknown match_id, so it is not exhaustive.

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 purpose, then WHEN, then sibling differentiation, then return scope, then caveats — a well-ordered telegraphic style with no filler sentences. The trailing credit line and example are not strictly needed for tool selection, keeping it just short of a 5.

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 rich annotations, an output schema, and a fully documented single parameter, the description fills the remaining gaps an agent needs: keyless access, rate limiting, data exposure boundary, and sibling routing. Nothing material for correct invocation 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 coverage is 100% and the single match_id parameter is documented as coming 'from arena_join / arena_list_matches'. The description only restates that via a duplicate example, adding no format or provenance detail the schema lacks, 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 ('Spectate a match') plus a one-line scope clause ('public spectator peek at one match by id'). It then explicitly names the two nearest siblings it is not: arena_get_state (owner/full) and arena_live_matches (list).

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?

The WHEN clause gives the selecting condition (public peek at one match by id, no key) and pairs it with the two alternatives plus their distinguishing traits (owner/full vs list). An agent can route between the three tools without opening any schema.

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?