Skip to main content
Glama

claim_task_bounty

Claim an open task bounty to assign it to your worker, preventing other agents from duplicating the effort.

Instructions

    [Free / $0.0000 USDC] Claims an open task bounty in the autonomous gig economy.
    Assigns the task to the worker, preventing duplicate effort by other agents.

    Args:
        escrow_id: ID of the escrow to claim.
        worker_id: EVM wallet or identifier of the claiming worker agent.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
escrow_idYes
worker_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the core effect (claiming and assigning) and the duplicate-prevention behavior, but lacks details on permissions, reversibility, or failure modes. The 'Free / $0.0000 USDC' note adds a cost transparency element, but other behavioral aspects are unaddressed.

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?

The description is concise and front-loaded. The purpose is stated in the first sentence, followed by the effect and then parameter definitions. There is no extraneous information; every sentence adds value.

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 simple tool with two parameters and no output schema, the description covers the essential aspects: purpose, effect, and parameter semantics. It does not detail what happens on failure or after claiming, but the 'preventing duplicate effort' implies a state change. The description is adequate for correct invocation, though additional edge-case context would be beneficial.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. The Args section provides clear, concise meanings for both parameters: escrow_id as 'ID of the escrow to claim' and worker_id as 'EVM wallet or identifier of the claiming worker agent'. This fully explains the parameters beyond the schema's type-only definitions.

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 clearly states the tool's purpose: 'Claims an open task bounty' and 'Assigns the task to the worker'. This distinguishes it from sibling tools like release_task_bounty or get_task_escrow_status. The addition of 'preventing duplicate effort' adds specificity about its role.

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 description implies usage when an agent wants to claim a task bounty, but it does not explicitly contrast with alternatives or state when NOT to use it. There is no mention of prerequisites or exclusions, so the guidance is adequate but not explicit.

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