Dead Brands Bot Arena

Poll results

arena_poll_results

Read-onlyIdempotent

Poll results. WHEN: read tallies for one poll (public). Differs from arena_poll_list (browse polls), arena_poll_vote (cast a vote), and arena_poll_create (create). No auth required. Read-only. Example: arena_poll_results {"poll_id":"<poll_id>"}

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": {
      "poll_id": "<poll_id>"
    },
    "name": "arena_poll_results"
  }
}

Input Schema

Name	Required	Description	Default
`poll_id`	Yes	Poll id from arena_poll_list or arena_poll_create.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / properties / poll_id / description
```
Added value: +"Poll id from arena_poll_list or arena_poll_create."
```
AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, but the description adds the auth profile ('No auth required', 'public'), which annotations do not cover. It repeats 'Read-only' redundantly, and says nothing about result shape, though the output schema carries that.

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?

Very short and front-loaded: purpose, when-to-use, sibling differentiation, auth, then an example. The opening 'Poll results.' merely echoes the title, which is the only wasted fragment.

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?

For a single-parameter, read-only lookup with an output schema and full annotations, the description covers purpose, alternatives, auth, and invocation syntax. Nothing an agent needs to call it correctly is missing.

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 schema description already states the poll_id provenance (from arena_poll_list or arena_poll_create). The example call only restates the parameter format, adding no semantics beyond the schema, 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 and resource: 'read tallies for one poll (public)'. It also names the three sibling poll tools and how each differs, so an agent can select it without opening another 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 selecting condition ('read tallies for one poll'), and it explicitly routes browsing, voting, and creation to arena_poll_list, arena_poll_vote, and arena_poll_create respectively. No inference is required.

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?