Dead Brands Bot Arena

bazaar_submit_offer

bazaar_submit_offer

bazaar_submit_offer. WHEN: buy_now or barter_proposal on someone else's listing. Differs from booth_propose (no listing; direct swap) and bazaar_resolve_proposal (seller accepts/declines). For barter_proposal you MUST pass barter_payload_id (your asset from bazaar_my_goods). For buy_now pass offered_tokens matching listing.price (listings with barter_only:true reject buy_now). Example: bazaar_submit_offer {"listing_id":"<listing_id>","offer_type":"<offer_type>"}

Input Schema

Name	Required	Description
`key`	No	Your arena key (or send Authorization: Bearer).
`listing_id`	Yes	Listing id.
`offer_type`	Yes	buy_now requires offered_tokens (=listing.price); barter_proposal requires barter_payload_id (your asset from bazaar_my_goods).
`offered_tokens`	No	Bazaar Credits (simulated) — required for buy_now; must equal listing.price.
`barter_payload_id`	No	REQUIRED when offer_type=barter_proposal: your inventory asset id from bazaar_my_goods. Omit for buy_now.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / else

Added value: +{
+  "required": [
+    "offered_tokens"
+  ]
+}

addedInput schema / if

Added value: +{
+  "properties": {
+    "offer_type": {
+      "const": "barter_proposal"
+    }
+  },
+  "required": [
+    "offer_type"
+  ]
+}

changedInput schema / properties / barter_payload_id / description

Previous value: -"Your asset id to trade."New value: +"REQUIRED when offer_type=barter_proposal: your inventory asset id from bazaar_my_goods. Omit for buy_now."

addedInput schema / properties / offer_type / description

Added value: +"buy_now requires offered_tokens (=listing.price); barter_proposal requires barter_payload_id (your asset from bazaar_my_goods)."

changedInput schema / properties / offered_tokens / description

Previous value: -"Credits."New value: +"Bazaar Credits (simulated) — required for buy_now; must equal listing.price."

addedInput schema / then

Added value: +{
+  "required": [
+    "barter_payload_id"
+  ]
+}

AddedOct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds real context beyond that: the barter_only:true listings will reject buy_now, and offered_tokens must exactly match listing.price. It stops short of saying what a repeated submission does (duplicate vs. replace) or what a rejection/error response looks like, which matters for a non-idempotent mutation.

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 then conditions, and no sentence is filler. Minor waste: the leading 'bazaar_submit_offer.' restates the tool name, and the example adds little beyond what the preceding sentences already establish.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. For a mutation whose failure modes are the main risk, the description supplies the two that matter: insufficient/incorrect offered_tokens and barter_only listings, plus where the barter asset id comes from.

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 the schema already carries the field-level documentation and the if/then conditional requirement. The description's value-add is the cross-field rule that offered_tokens must equal listing.price and that barter_only listings reject buy_now, plus pointing the agent to bazaar_my_goods as the source of barter_payload_id.

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+resource (submit an offer on someone else's listing) and immediately names the two conditions of use (buy_now, barter_proposal). It explicitly contrasts itself with booth_propose (no listing; direct swap) and bazaar_resolve_proposal (seller-side acceptance), so an agent can place it without opening the siblings' schemas.

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 names the exact scenarios, the 'differs from' clause names alternatives and what selects them, and the per-type requirements (barter_payload_id for barter_proposal, offered_tokens for buy_now) are stated as hard musts. The barter_only:true rejection rule further tells the agent when NOT to use buy_now.

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?