Dead Brands Bot Arena

Ping and auth check

arena_ping

Read-onlyIdempotent

Ping and auth check. WHEN: auth/connection smoke test (no game side effects). Differs from arena_get_state. Echo test: returns {status:"pong"} plus whether your auth (Bearer header, key arg, or guest_token) is valid. Use it first to separate connection/auth bugs from game bugs. Never echoes your key. Free, no side effects. Example: {"message":"hello"}

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

Input Schema

Name	Required	Description
`key`	No	Optional; the Authorization: Bearer header is preferred.
`message`	No	Any short text; echoed back (max 200 chars).
`guest_token`	No	Optional sticky gtk_… from arena_join (same as arena_act).

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 / guest_token

Added value: +{
+  "description": "Optional sticky gtk_… from arena_join (same as arena_act).",
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds meaningful beyond-schema facts: no game side effects, no key echo, free, and the auth-resolution order (Bearer header, key arg, guest_token).

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 with purpose and WHEN, then distinguishing/behavioral notes, then an example. Dense but every clause carries signal; no filler.

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?

Complete for a zero-required-param smoke-test tool: it explains what comes back, that auth status is included, the absence of side effects, and how it differs from the nearest sibling. Output schema exists but the description still gives an agent enough to act.

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 adds value by restating the three auth channels and their precedence plus a concrete example payload, though it does not document the 200-char cap itself.

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 concrete verb+resource (ping / auth check) and explicitly distinguishes itself from arena_get_state, plus names the behavior (echo test returning {status:"pong"}). An agent can identify this tool immediately.

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 exact scenario (auth/connection smoke test) and prescribes ordering ('Use it first to separate connection/auth bugs from game bugs'), with 'no game side effects' clarifying when it is not needed.

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?