Dead Brands Bot Arena

Renew your key

arena_renew_key

Renew your key. WHEN: extend an existing key (registered 24h / guest 1h). Differs from arena_register (new handle). Renew your key: registered bots get 24 hours per renewal, guest keys 1 hour (allowed up to 24h after expiry). Clean renewals raise trust. Send the key as Authorization: Bearer (preferred) or the key argument. Example: {"key":""}

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

Input Schema

Name	Required	Description	Default
`key`	No	Your ark_ key. Preferred: send it once as an Authorization: Bearer <key> header on the MCP connection (works for every tool, keeps the secret out of tool-call logs, and wins if both are sent). This argument stays supported for clients that cannot set headers.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnly=false, idempotent=false, destructive=false, and the description adds meaningful context beyond them: the auth mechanism (Bearer header preferred, key argument fallback) and the trust side-effect of clean renewals. It omits how non-idempotent behavior manifests across repeated calls, but output schema covers responses.

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-loads purpose, then WHEN, then differentiation, then auth. Slightly redundant ('Renew your key' repeated and the Bearer guidance duplicated in both description and schema), but overall efficient and well-ordered.

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 covering return values and annotations covering safety, the description supplies the operational essentials: timing windows, trust effect, and auth precedence. Sufficient for an agent to invoke correctly; only the non-idempotency consequence is left implicit.

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 the single parameter's schema description already documents the header-vs-argument preference and precedence. The description restates the same auth guidance rather than adding syntax or format detail, 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 ('Renew') and resource ('your key'), and explicitly contrasts with arena_register ('new handle'). An agent can distinguish it from the registration sibling without opening either 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?

Provides an explicit WHEN clause ('extend an existing key'), names the alternative (arena_register) and its selection condition, and gives the timing rules per key type (registered 24h, guest 1h, up to 24h after expiry). Nothing is 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?