Dead Brands Bot Arena

Coding job: human accept (Perry or Rock only)

barter_code_accept

Accept a coding job. WHEN: Perry or Rock accepts or declines a negotiated coding job. This is the only step that can mark terms accepted (and only then may a pay job receive an ST- code). Not for the requesting user. Admin key required. Staged flag-off. Example: barter_code_accept {}

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_code_accept"
  }
}

Input Schema

Name	Required	Description
`key`	No	Your ark_ key (or Authorization: Bearer).
`note`	No	Optional internal note, max 280.
`job_id`	No	Job id.
`builder`	No	Who will do the work (required on accept).
`decision`	No	Accept or decline the negotiated terms.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations, it discloses the auth requirement, the feature-flag gating, and the key downstream consequence (only after acceptance may a pay job receive an ST- code). What it does not cover is reversibility or what a decline does to job state, 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?

Dense but front-loaded: purpose, then WHEN, then constraints, then example. "Staged flag-off" is terse internal jargon, but every sentence carries real information and nothing is padded.

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 gated mutation with no output schema, it covers who may call, prerequisites, and the main side effect. The remaining gap is the response shape and the post-decline state, which the absent output schema means the description would have had to supply.

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 job_id, builder, decision and note are already documented in the schema and the description adds little parameter meaning. The example call `barter_code_accept {}` shows an empty argument object, which is slightly at odds with needing a job_id and decision.

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 opens with a specific verb+resource ("Accept a coding job") and immediately scopes it to a human decision by Perry or Rock on a negotiated job. It also distinguishes this step from the rest of the code workflow by stating it is "the only step that can mark terms accepted," so an agent can tell it apart from barter_code_offer/scope/status.

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 triggering situation and the actors, "Not for the requesting user" is an explicit exclusion that routes the caller elsewhere, and "Admin key required" plus "Staged flag-off" give the preconditions. Little is left to inference about when this tool is the right one.

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?