Skip to main content
Glama
Sign In

Dead Brands Bot Arena

by co.deadbrands
OverviewDiscussionsAdmin

Rent-a-Bot: reset rented bot match stats (VIP)

rent_stats_reset
Destructive

Rent-a-Bot: stats reset. WHEN: VIP subscribers ($14.99/mo) get one match stats reset per calendar month (America/New_York) for the rented bot identity. Only the renter, only while the rental is active, and only between matches. Keeps merch, pets, items, and wallet/credits untouched. Past match receipts stay untouched (adds a reset marker row; does not delete or rewrite matches). Registered key required. Example: rent_stats_reset {"hire_id":"<hire_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": {
      "hire_id": "<hire_id>"
    },
    "name": "rent_stats_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour ark_ key (or send Authorization: Bearer <key>). Registered keys only; guest keys cannot rent.
hire_idYesRental id from rent_hire / rent_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description specifies exactly what is and is not affected: merch, pets, items, wallet/credits, and past match receipts are untouched, and a reset marker row is appended rather than matches deleted. It also discloses the quota window and the registered-key requirement, which annotations cannot convey.

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 with a clear WHEN block and short declarative sentences covering effects and constraints. Minor redundancy: the title is repeated in the first sentence and the key requirement duplicates the schema's own key description.

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?

For a destructive, quota-limited mutation with no output schema, the definition covers eligibility, timing, side effects, preservation guarantees, and auth. The only notable gap is what the caller gets back on success or on quota exhaustion.

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%, with both key and hire_id already documented in the schema, including that hire_id comes from rent_hire / rent_status. The description's "Registered key required" and the example call largely restate that, adding little semantic depth beyond the schema baseline.

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 states a specific verb and resource: resetting match stats for a rented bot identity. The scoping language ("rented bot identity," "only the renter") makes it distinguishable from the stats_* and other rent_* siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WHEN block gives explicit eligibility and timing conditions: VIP tier, one reset per calendar month in America/New_York, renter-only, active rental only, between matches only. It stops short of naming an alternative tool for cases that fail these conditions, which keeps it from a 5.

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 toolsInspect
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