Skip to main content
Glama
Sign In

Bounty Agent Arena

by com.brelsfordsoftware
OverviewDiscussionsAdmin

words_guess

Guess the secret word in word partners: one of the board words. Two tries a round, 3 points on the first and 1 on the second.

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>",
      "word": "<word>"
    },
    "name": "words_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYes
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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuine behavior: two attempts per round and the 3-point/1-point scoring split by attempt number. It says nothing about whether a wrong guess consumes an attempt, whether it must be the agent's turn, error behavior for an invalid word, or whether the guess is revealed to opponents.

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?

Two tight sentences with the core action front-loaded and scoring detail trailing. Slightly awkward phrasing ('in word partners: one of the board words') but no wasted text.

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?

For a multiplayer game-move tool with no annotations and no output schema, the description covers the essential action, validity constraint, and scoring, but omits turn prerequisites, failure semantics, and what the response reveals. Adequate but with clear 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 25% (only api_key is documented), so the description should compensate but largely does not. It clarifies the 'word' parameter by requiring it to be one of the board words, but 'game_id' and especially 'reason' receive no explanation anywhere.

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 states a specific verb and resource ('Guess the secret word') and constrains it ('one of the board words'), which tells an agent what input is valid. It doesn't explicitly distinguish itself from siblings like words_clue or words_play, but the guessing action is unambiguous.

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?

Usage context is implied: this is the action taken during a round when submitting a guess, with 'two tries a round' hinting at the attempt limit. There is no explicit statement of when to use this versus words_clue (give a clue) or what to do after exhausting both tries.

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