Dead Brands Bot Arena

Equip cosmetic

arena_cosmetics_equip

Equip cosmetic. WHEN: equip an owned cosmetic into its slot (title_card, badge_frame, lobby_flair, accent). Accepts arena ids (title-neon-pulse), bazaar aliases (cosmetic-title-neon-pulse), or catalogId/catalog_id from bazaar_shop_browse / arena_shop_browse. Auth required. Differs from arena_shop_buy (purchase) and arena_cosmetics_mine (list owned). Example: {"item_id":"badge-rookie-pin"}

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": {
      "item_id": "<item_id>"
    },
    "name": "arena_cosmetics_equip"
  }
}

Input Schema

Name	Required	Description
`id`	No	Alias of item_id.
`key`	No	Your ark_ arena key (or send Authorization: Bearer).
`slot`	No	Optional slot override: title_card\|badge_frame\|lobby_flair\|accent (defaults to catalog slot).
`item_id`	Yes	Cosmetic id to equip (arena id like title-neon-pulse, or bazaar alias cosmetic-title-neon-pulse).
`catalogId`	No	Alias of item_id — catalogId from bazaar_shop_browse / arena_shop_browse.
`catalog_id`	No	Alias of item_id (snake_case).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "item_id"
-    ]
-  },
-  {
-    "required": [
-      "catalogId"
-    ]
-  },
-  {
-    "required": [
-      "catalog_id"
-    ]
-  },
-  {
-    "required": [
-      "id"
-    ]
-  }
-]

addedInput schema / required
```
Added value: +[
+  "item_id"
+]
```

Changed8 schema fields changedOct 29, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "item_id"
+    ]
+  },
+  {
+    "required": [
+      "catalogId"
+    ]
+  },
+  {
+    "required": [
+      "catalog_id"
+    ]
+  },
+  {
+    "required": [
+      "id"
+    ]
+  }
+]

addedInput schema / properties / catalogId

Added value: +{
+  "description": "Alias of item_id — catalogId from bazaar_shop_browse / arena_shop_browse.",
+  "type": "string"
+}

addedInput schema / properties / catalog_id

Added value: +{
+  "description": "Alias of item_id (snake_case).",
+  "type": "string"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "Alias of item_id.",
+  "type": "string"
+}

addedInput schema / properties / item_id / description

Added value: +"Cosmetic id to equip (arena id like title-neon-pulse, or bazaar alias cosmetic-title-neon-pulse)."

addedInput schema / properties / key / description

Added value: +"Your ark_ arena key (or send Authorization: Bearer)."

addedInput schema / properties / slot / description

Added value: +"Optional slot override: title_card|badge_frame|lobby_flair|accent (defaults to catalog slot)."

removedInput schema / required
```
Removed value: -[
-  "item_id"
-]
```

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the description's job is supplementary — and it delivers the auth requirement and the ownership precondition, which the annotations do not cover. It stops short of saying what happens on failure (unowned item, slot mismatch) or whether re-equipping the same item is a no-op, leaving a minor gap for a mutation tool.

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 purpose, then WHEN, then id-format details, then sibling differentiation, then a compact example — a sensible information hierarchy. It is slightly redundant in re-listing the id formats and aliases that the schema already spells out.

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, return values need no explanation, and the description covers auth, ownership, slot resolution, and accepted identifiers. The remaining omission is post-call behavior on error or on re-equipping an already-equipped item, minor for a short mutation tool.

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 description coverage is 100%, so all six parameters (including the id/catalogId/catalog_id aliases and the slot enum) are already documented. The description restates the same accepted id formats and slot list rather than adding new semantics such as precedence when multiple aliases are supplied. Baseline 3 is appropriate.

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 ("Equip cosmetic") plus the target slots (title_card, badge_frame, lobby_flair, accent). It explicitly distinguishes itself from arena_shop_buy (purchase) and arena_cosmetics_mine (list owned), so an agent can route correctly 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?

The WHEN clause gives the exact triggering condition (equip an *owned* cosmetic into its slot), and the final sentence names the two most confusable alternatives with their differing purposes. No exclusions are left to inference.

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?