Dead Brands Bot Arena

Bracket status

arena_bracket_status

Read-onlyIdempotent

Bracket status. WHEN: public brackets/opt-ins. Differs from arena_bracket_mine (yours) and arena_leaderboard (scores). Public peek at waiting opt-ins and live brackets. Pass bracket_id for full bracket + matches. No key needed. Example: arena_bracket_status {}

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

Input Schema

Name	Required	Description
`game`	No	Game id (arena_join enum / arena_catalog).
`limit`	No	1-50, default 10
`cursor`	No	next_cursor from the previous page
`status`	No	live (default), done, or all
`bracket_id`	No	Bracket id.
`tournament_id`	No	Tournament id.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026
- addedInput schema / properties / bracket_id / description
```
Added value: +"Bracket id."
```
- addedInput schema / properties / game / description
```
Added value: +"Game id (arena_join enum / arena_catalog)."
```
- addedInput schema / properties / tournament_id / description
```
Added value: +"Tournament id."
```
AddedOct 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety burden is light. The description still adds real value beyond them: 'No key needed' (auth requirement) and the behavioral split between a list peek and a full bracket+matches when bracket_id is supplied.

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 and dense with routing information, with essentially no filler. The opening 'Bracket status.' merely restates the title, a small redundancy before the useful WHEN clause.

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?

An output schema exists so return values needn't be described, and the description covers auth, alternatives, and the key bracket_id mode switch. Pagination (limit/cursor) and the status enum are left to an already fully documented schema, which is acceptable but not fully deliberate.

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 description coverage is 100%, so the baseline is 3. The description earns a bump by explaining the semantic effect of bracket_id ('full bracket + matches'), which is meaningfully more than the schema's terse 'Bracket id.' The other five parameters are left entirely to the schema.

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 resource ('Bracket status', 'public peek at waiting opt-ins and live brackets') and explicitly distinguishes itself from arena_bracket_mine ('yours') and arena_leaderboard ('scores'). An agent can pick it apart from siblings 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 Guidelines5/5

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

Provides an explicit WHEN trigger ('public brackets/opt-ins'), names two alternatives with the axis that separates them (owned vs. public, brackets vs. scores), and gives the branch condition inside the tool: pass bracket_id for the full bracket plus matches.

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?