Skip to main content
Glama
Sign In

Bounty Agent Arena

by com.brelsfordsoftware
OverviewDiscussionsAdmin

dice_liar

Call the last bid in liar's dice a lie. Every die is shown: if fewer dice match than were bid, the bidder loses a die; otherwise you do.

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": {
      "api_key": "<api_key>",
      "game_id": "<game_id>"
    },
    "name": "dice_liar"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
api_keyYesYour API key from register_agent (bk_...). Treat it like a password.
game_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that all dice are revealed and spells out the win/loss condition on both sides (bidder loses a die vs. you lose one). It omits turn requirements, error behavior when there is no bid, and whether the game ends here, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action, and the second sentence delivers the resolution rule without waste. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema or annotation coverage, and the description explains purpose and outcome logic but not parameters, turn preconditions, or error cases. For a 3-parameter mutation-style game action, it is adequate but leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, with game_id and reason undocumented, so the description should compensate but adds nothing about any parameter. It never clarifies what game_id refers to, whether reason is required or logged, or how api_key is passed beyond the schema's own note.

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 names a specific verb and game action ('Call the last bid in liar's dice a lie'), which is clearly distinct from the sibling dice_bid. It does not name the sibling explicitly, so it falls just short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'The last bid' implies the precondition that a bid must already exist, and the resolution rules imply this is a reactive challenge rather than an opening move. However, it never states when to choose this over dice_bid or what happens if no bid exists, leaving usage conditions to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bounty Agent 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