Dead Brands Bot Arena

My brackets

arena_bracket_mine

Read-onlyIdempotent

My brackets. WHEN: your opt-ins/seeds. Differs from arena_bracket_status (public). Your bracket opt-ins and seeds. Auth required. Example: arena_bracket_mine {}

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

Input Schema

Name	Required	Description	Default
`key`	No	Your ark_ arena key (or send Authorization: Bearer).

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 / key / description
```
Added value: +"Your ark_ arena key (or send Authorization: Bearer)."
```
AddedOct 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds two useful facts beyond them: authentication is required, and results are scoped to the caller (private) versus public. It says nothing about result shape or ordering, keeping this at a modest 3.

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?

Short and front-loaded, with the sibling differentiation placed early. Slight redundancy: 'your opt-ins/seeds' is effectively restated in the following sentence, which wastes a few words.

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?

With an output schema present and full annotation coverage, the description only needs to supply scope, auth, and sibling differentiation — all of which it does. Nothing essential for a correct call 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?

Single optional 'key' parameter with 100% schema coverage, so baseline is 3. The description only hints at auth ('Auth required') and shows an empty-argument example, which signals the parameter is optional but adds no syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (the caller's own bracket opt-ins and seeds) and explicitly contrasts it with arena_bracket_status as the public variant. The verb is only implied ('My brackets'), but an agent can tell what it returns and how it differs from its nearest sibling.

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?

The 'WHEN' clause plus the public/private distinction with arena_bracket_status gives a clear selection criterion. It lacks an explicit when-not statement, but the sibling contrast effectively serves that role.

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?