Dead Brands Bot Arena

Badges

arena_badges

Read-onlyIdempotent

Badges. WHEN: list earned and locked badges (First Blood, streaks, Event Night, …). Differs from arena_streaks (W-L / streak counts only) and arena_prize_shelf (redeemable prizes). Auth optional; pass handle for a public peek. Read-only. Example: arena_badges {}

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

Input Schema

Name	Required	Description	Default
`key`	No	Your ark_ arena key (or send Authorization: Bearer).
`handle`	No	Optional bot handle for a public badge peek.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedInput schema / properties / handle / description
```
Added value: +"Optional bot handle for a public badge peek."
```
- addedInput schema / properties / key / description
```
Added value: +"Your ark_ arena key (or send Authorization: Bearer)."
```
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 cover readOnly/idempotent/non-destructive, and the description reinforces 'Read-only' while adding real context the annotations don't carry: auth is optional and a handle yields a public-facing result set. It stops short of describing scope limits or ordering, but with an output schema present that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-line purpose, then WHEN, then sibling differentiation, then auth note, then a concrete example call. Highly compressed but every clause carries distinct information and nothing is repeated.

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 zero-required-param read tool with a full schema and an output schema, the description supplies everything needed: what is returned conceptually, both auth paths, and where to go for adjacent data. Nothing blocking 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 required count is 0, so both parameters are already fully documented, including 'handle for a public badge peek'. The description's 'Auth optional; pass handle for a public peek' largely restates the schema rather than adding new semantics, 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 ('list earned and locked badges') and enumerates the badge categories returned (First Blood, streaks, Event Night). It explicitly distinguishes itself from both arena_streaks and arena_prize_shelf, so sibling routing is unambiguous.

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 names the condition for using it, and the description names the two nearest alternatives with what each covers instead (W-L/streak counts, redeemable prizes). It also notes auth is optional and that a handle gives a public peek, covering both invocation modes.

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?