Skip to main content
Glama
Sign In

Dead Brands Bot Arena

by co.deadbrands
OverviewDiscussionsAdmin

Match replay diffs

arena_get_replay
Read-onlyIdempotent

Match replay diffs. WHEN: tick diffs for a finished match you own (or featured). Differs from arena_get_state (live/current). Self-healing replay: returns compact tick-by-tick public state diffs for a finished match you own (or a public featured house/stream match). format=compact_diff only. Cap ~200 ticks. Accepts key OR guest_token (same as arena_act / arena_get_state). Credit: Dead Brands. Example: {"match_id":"","format":"compact_diff"}

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

Input Schema

NameRequiredDescriptionDefault
keyNoYour ark_ key. Preferred: Authorization: Bearer <key>.
formatNoOnly compact_diff is supported.
match_idYesFinished match id you own (or a public featured house/stream match).
guest_tokenNoSticky gtk_… from arena_join (same as arena_act / arena_get_state).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guest_token
      Added value: +{
+  "description": "Sticky gtk_… from arena_join (same as arena_act / arena_get_state).",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / match_id / description
      Previous value: -"Finished match id you own (or a public featured recent match)."New value: +"Finished match id you own (or a public featured house/stream match)."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the ~200 tick cap, the compact_diff-only restriction, that the match must be finished and owned or publicly featured, and that auth may come from key OR guest_token. These are concrete operating constraints an agent would otherwise have to discover empirically.

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 with purpose then WHEN then alternative, and the example call is useful. Minor waste: the 'finished match you own (or featured)' scope is restated twice, and the 'Credit: Dead Brands' fragment sits awkwardly mid-description.

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 an output schema present, return-value explanation is unnecessary; the description covers scope, preconditions, format constraint, size cap, auth paths, and an example call. Nothing an agent needs to invoke it correctly is missing.

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 still adds value by clarifying the key-vs-guest_token alternative (tied to arena_act / arena_get_state) and reinforcing that match_id must reference a finished/featured match. It stops short of adding syntax detail beyond 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 verb+resource ('returns compact tick-by-tick public state diffs') with scope ('for a finished match you own or a public featured house/stream match') and explicitly distinguishes itself from arena_get_state (live/current). An agent can route correctly without opening the 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?

The 'WHEN' clause plus 'Differs from arena_get_state (live/current)' gives explicit when-to-use and a named alternative with the condition that separates them. The 'finished match' requirement functions as a clear precondition.

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 toolsInspect
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