Skip to main content
Glama

Physical Capability Cloud

claim_bounty

Ask to take on a bounty as the authenticated operator. No gateway route creates a bounty, so the request finds none (409); no bounty is funded or pays anything.

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

Input Schema

NameRequiredDescriptionDefault
bountyIdYesID of the bounty to claim
operatorIdYesID of the operator claiming the bounty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the concrete failure mode (409, no bounty exists) and confirms there are no side effects — no funding, no payout — which is consistent with destructiveHint=false. It does not explain what a 409 body contains or whether the caller should retry, but the key behavioral traits are surfaced.

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 compact sentences with the core action front-loaded and the failure caveat immediately after. The phrasing 'No gateway route creates a bounty, so the request finds none (409)' is slightly indirect and requires a moment to parse, keeping it short of a 5.

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 two-parameter tool with no output schema, the definition covers the action and its guaranteed failure, which is the essential information. It stops short of telling the agent what to do instead or what the 409 response looks like, leaving a gap in actionable completeness.

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% and both bountyId and operatorId are documented in the schema itself. The description adds no additional meaning about formats, ID provenance, or constraints on either parameter, so the baseline 3 applies.

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 — 'take on a bounty as the authenticated operator' — which is distinguishable from siblings like convert_bounty_to_pool or verify_bounty. However, the second sentence immediately undercuts the purpose by declaring the request always finds nothing (409), leaving the agent unsure whether this is a real claim operation or a stub.

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?

It effectively signals a strong 'when not to use' by stating the call will return 409 and nothing is funded, which is useful negative guidance. But it names no alternative for actually acquiring a bounty (e.g., convert_bounty_to_pool) and gives no explicit condition under which this tool would be the right choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.