Skip to main content
Glama
Sign In

Dead Brands Bot Arena

by co.deadbrands
OverviewDiscussionsAdmin

Plans: start an order

plan_checkout

Plans: checkout. WHEN: buy a plan, add-on, or the limited T-Rex (sku pet_trex, $1.99 one-time, edition of 500). Returns an order code (DB-XXXXXX). Rent-a-Bot plan checkout stays closed until Nov 16 (waitlist). The T-Rex is on sale now: pay with X Money, PayPal (one-time capture), or USDC on Base, then claim with pet_buy. Send idempotency_key so a retry never makes a second order. Registered key required. Example: plan_checkout {"sku":""}

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": {
      "sku": "<sku>"
    },
    "name": "plan_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour ark_ key (or send Authorization: Bearer <key>). Registered keys only.
skuYeshouse_bot ($4.99 30-day pass), vip ($14.99 30-day pass), credits_100 ($2.99), godmode_1 ($2.99), godmode_3 ($6.99), pet_trex ($1.99 limited T-Rex, edition of 500, on sale now).
payment_methodNox_money (default), paypal (plans: subscription; pet_trex: one-time $1.99 capture), or usdc (pet_trex on Base only).
idempotency_keyNoClient-chosen id. Same key = same order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / payment_method / description
      Previous value: -"When checkout is open: x_money (default) or paypal (house_bot/vip subscription approve URL)."New value: +"x_money (default), paypal (plans: subscription; pet_trex: one-time $1.99 capture), or usdc (pet_trex on Base only)."
    • changedInput schema / properties / payment_method / enum
      Previous value: -[
-  "x_money",
-  "paypal"
-]New value: +[
+  "x_money",
+  "paypal",
+  "usdc"
+]
    • changedInput schema / properties / sku / description
      Previous value: -"house_bot ($4.99 30-day pass), vip ($14.99 30-day pass), credits_100 ($2.99), godmode_1 ($2.99), godmode_3 ($6.99)."New value: +"house_bot ($4.99 30-day pass), vip ($14.99 30-day pass), credits_100 ($2.99), godmode_1 ($2.99), godmode_3 ($6.99), pet_trex ($1.99 limited T-Rex, edition of 500, on sale now)."
    • changedInput schema / properties / sku / enum
      Previous value: -[
-  "house_bot",
-  "vip",
-  "credits_100",
-  "godmode_1",
-  "godmode_3"
-]New value: +[
+  "house_bot",
+  "vip",
+  "credits_100",
+  "godmode_1",
+  "godmode_3",
+  "pet_trex"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / payment_method
      Added value: +{
+  "description": "When checkout is open: x_money (default) or paypal (house_bot/vip subscription approve URL).",
+  "enum": [
+    "x_money",
+    "paypal"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description carries real weight here and does: registered key required for auth, per-method payment semantics (paypal one-time capture, usdc on Base only), and the order-code return format. Conditional idempotency via key is consistent with idempotentHint=false. It stops short of describing failure modes (declined payment, sold-out T-Rex), which keeps it at 4.

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 purpose and WHEN, and the key operational constraints appear early. Some duplication of schema content (T-Rex price/edition appears twice, payment method names restated) and mildly promotional phrasing ("on sale now") cost a point.

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?

No output schema, but the description supplies the order-code shape and the downstream claim step, so an agent knows what happens after a successful call. What is missing is error behavior and what a returned order code is redeemable for in terms of timing/expiry.

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?

Schema coverage is 100%, so baseline is 3, but the description adds intent the schema lacks: the idempotency_key is explained by its purpose ("a retry never makes a second order") and the sku parameter is tied to the pay-then-claim flow. The payment_method and pricing details are largely restated from the enum descriptions, limiting the uplift.

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 ("checkout" / start an order for a plan or SKU) and immediately names the objects it applies to (plan, add-on, pet_trex) plus the return artifact (order code DB-XXXXXX). It is distinguishable from sibling pet_buy, which is framed as the later claim step.

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?

Uses an explicit WHEN clause, routes the post-payment step to pet_buy, and flags an availability gate (Rent-a-Bot closed until Nov 16, waitlist). It also states the retry condition (send idempotency_key) rather than leaving it 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 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