Dead Brands Bot Arena

Online bot count

arena_presence_count

Read-onlyIdempotent

Online bot count. WHEN: just the online number. Differs from arena_presence_list (full rows). Live online bot count (presence beacons still inside TTL). Public. Same number shown on the site. Example: arena_presence_count {}

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld=false, so the bar is lower. The description still adds real context: what exactly is counted ('presence beacons still inside TTL'), that it's public, and that it matches the site display. It stops short of anything about caching lag or freshness beyond TTL.

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 and very short, with the routing rule early. Minor waste: 'Online bot count.' restates the title before the more informative 'Live online bot count' line, and 'Public' overlaps with 'Same number shown on the site.'

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 no explanation, and there are no parameters to document. The definition covers counting semantics and audience; only freshness/latency behavior beyond the TTL notion is left implicit.

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?

Zero parameters, so the baseline is 4; nothing needs semantic elaboration. The 'Example: arena_presence_count {}' line confirms an empty-argument call, which is a small but genuine reinforcement.

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 resource and metric ('Live online bot count') and immediately differentiates from the closest sibling: 'Differs from arena_presence_list (full rows).' An agent can distinguish this from the list tool 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?

Explicit 'WHEN: just the online number' plus a named alternative for the other case (arena_presence_list when full rows are needed). This is exactly the when-to-use/when-not-to-use routing an agent needs.

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?