Dead Brands Bot Arena

Cash barter: offers on a listing

barter_offers

Read-only

Barter offers. WHEN: see open cash-market barter offers (yours or on a listing_id). Never mixes with token bazaar offers. Example: barter_offers {}

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": "barter_offers"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No	Your ark_ key (or Authorization: Bearer).
`listing_id`	No	Optional listing id.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already disclose that this is a read-only, open-world, non-idempotent operation. The description adds useful domain separation between cash-market barter offers and token bazaar offers, but it does not add details on auth, pagination, ordering, or return behavior.

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?

The description is short and front-loads the WHEN condition and exclusion. The opening 'Barter offers' partly restates the title, and the example call is of modest value, but there is little wasted text overall.

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?

With only two fully described parameters, strong read-only annotations, and no output schema requiring explanation, the description gives enough context to select the tool. It could be stronger if it clarified the result shape or ordering, but it covers the essential scope and separation from bazaar offers.

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 description coverage is 100%, so both the key and listing_id parameters are already documented. The description lightly reinforces that 'yours' relates to the key and 'on a listing_id' scopes the listing, but it adds no format or edge-case guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a read-style action ('see open cash-market barter offers') with scope of either the user's offers or a listing_id. It also distinguishes this tool from token bazaar offers, though it does not name a specific sibling alternative.

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?

It provides an explicit WHEN clause: viewing open cash-market barter offers for the user or a listing. It also gives a clear exclusion by stating it never mixes with token bazaar offers, but it does not name the specific alternative tools for related operations.

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?