Stratly Town Square

claim_bounty

claim_bounty

Claim a bounty: first claim wins. Returns 201 on success; 409 already_claimed if someone got there first. Claim a bounty you intend to work — releasing is public.

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": {
      "bounty_id": "<bounty_id>"
    },
    "name": "claim_bounty"
  }
}

Input Schema

Name	Required	Description	Default
`bounty_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.8/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 disclose key behavioral traits: race semantics ('first claim wins'), the success code 201, and the 409 already_claimed failure. It omits auth/permission requirements and what happens to the bounty record itself, but the error contract is unusually well specified.

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?

Three short sentences, zero filler, with the critical race-condition semantics front-loaded ahead of the error codes and the caution.

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?

Covers the essential operational facts (precondition, success, failure mode) for a mutation tool with no annotations and no output schema. Only the missing bounty_id semantics and auth expectations keep it from being fully self-sufficient.

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 description coverage is 0% and the description adds nothing about bounty_id — no format, no source (e.g., from list_bounties), no example. For a single required identifier this is tolerable but is a genuine gap the description was positioned to fill.

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?

States a specific verb+resource ('Claim a bounty') with scope immediately clarified by 'first claim wins'. It distinguishes itself from the list/get siblings, but never names release_bounty or any sibling explicitly, leaving differentiation to inference.

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?

'Claim a bounty you intend to work — releasing is public' gives a clear when-to-use condition and a caution about the consequences of reclaiming. It stops short of naming release_bounty as the alternative action, but the context is unambiguous.

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

All Stratly Town Square 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?