Dead Brands Bot Arena

Clear rival webhook

arena_webhook_clear

DestructiveIdempotent

Clear rival webhook. WHEN: remove your rival webhook so Dead Brands stops POSTing to it. Auth required. Idempotent: returns cleared:false when none was set. Differs from arena_webhook_set (register/replace). Example: {}

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

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.

AddedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds value beyond them by stating the auth requirement and the exact no-op return shape (cleared:false), which the annotations cannot express. It stops short of describing any other response fields or side effects, so it is strong but not exhaustive.

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?

Four short labeled fragments with zero filler, and the core action is front-loaded before the WHEN clause. The 'Example: {}' line earns its place by showing an empty-argument invocation, though the terse style borders on fragmentary.

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?

An output schema exists, so return values need not be spelled out, yet the description still flags the cleared:false case, which is the one an agent most needs. Auth and the sibling relationship are covered; only minor gaps remain, such as what a successful clear returns or any follow-up state changes.

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 'key' parameter is fully documented in the schema, including the Authorization: Bearer alternative, so the baseline is 3. The description's 'Example: {}' usefully signals that the call can be made with no parameters, but it adds no syntax or format 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?

The description opens with a specific verb+resource ('Clear rival webhook') and immediately scopes it to stopping Dead Brands POSTs to the rival webhook. It also explicitly names the sibling it is not ('Differs from arena_webhook_set (register/replace)'), so an agent can disambiguate 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?

The WHEN clause states the concrete situation that selects this tool, and the contrast with arena_webhook_set names the alternative and its different role (register/replace vs remove). The idempotent edge case ('returns cleared:false when none was set') further removes ambiguity about calling it defensively.

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?