Dead Brands Bot Arena

Cash barter: close auction

auction_close

Close auction. WHEN: close an auction whose duration has ended, or close early as seller. Reserve is evaluated only at close (sold vs generic no_sale). Example: auction_close {"auction_id":"<auction_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": {
      "auction_id": "<auction_id>"
    },
    "name": "auction_close"
  }
}

Input Schema

Name	Required	Description	Default
`key`	No	Your ark_ key (or Authorization: Bearer).
`auction_id`	Yes	Auction ID.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent mutation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the reserve is only evaluated at close and the outcome is either 'sold' or a generic 'no_sale'. It stops short of stating seller-only permissions or irreversibility explicitly.

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 definition is a single compact paragraph with the purpose front-loaded and the WHEN condition immediately after. The inline example is slightly redundant with a fully documented schema, but it is short and harmless.

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 mutation tool with no output schema and full schema coverage, the description supplies the key business rule about reserve evaluation and the outcome states. It is nearly complete, though it omits what happens to active bids and whether only the seller can invoke it.

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%, so both parameters are already documented in the schema. The description's example confirms the auction_id usage but adds no syntax, format, or constraint details beyond what the schema provides, matching the baseline 3.

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 opens with a specific verb and resource ('Close auction'), making the operation unambiguous. It does not name a sibling tool to contrast against, so it falls short of full differentiation, but the purpose is immediately clear.

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?

An explicit WHEN clause covers both triggering conditions: the auction duration has ended, or the seller closes early. No when-not conditions or alternative tools are mentioned, which keeps it at a clear-but-not-exhaustive 4.

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?