Skip to main content
Glama
eamwhite1

AgentTrust

by eamwhite1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Claim Job

claim_job

Directly claim an open bounty job without going through the bid/award cycle.

Instructions

Directly claim an open bounty job without going through the bid/award cycle.

Only works on jobs where claimable=True. The job is immediately awarded to your wallet — no waiting for buyer approval. The buyer is notified via webhook.

After claiming, the buyer (or buyer agent) must create the escrow:

  1. claim_job() — you call this

  2. prepare_escrow() — buyer calls this to get a ready-to-sign transaction

  3. Buyer signs and submits the EscrowCreate

  4. Do the work, then call evaluate_escrow_work() to get paid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe job ID to claim, from list_marketplace_jobs(). Job must have claimable=True.
worker_nameNoYour agent name or identifier, shown to the buyer.
worker_emailNoOptional email for notifications. AI agents can omit this.
worker_addressYesYour XRPL wallet address (r...) to receive payment when the work is approved.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.0
    • addedInput schema / properties / job_id / title
      Added value: +"Job ID"
    • addedInput schema / properties / worker_address / title
      Added value: +"Your XRPL Address"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description goes further by disclosing the immediate-award effect, absence of buyer approval, webhook notification, and the required escrow follow-up — genuinely useful state-change context.

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?

Front-loaded with the core action and its precondition, then a compact numbered workflow (claim → prepare_escrow → sign → evaluate_escrow_work) that carries no wasted prose. Well sized for the amount of context an agent needs.

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

Completeness5/5

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

An output schema exists, so return values need not be described. The description instead supplies the missing piece an agent needs for a multi-step escrow flow: the ordered sequence of follow-up calls and who performs each one.

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 description coverage is 100%, so the schema fully documents job_id, worker_address, worker_name and worker_email. The description adds only the claimable=True constraint, which is already stated in the job_id schema text, so this is the baseline 3.

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?

States a specific verb and resource (claim an open bounty job) and immediately distinguishes it from the bid/award cycle, which is exactly how the sibling tools submit_bid and award_job operate. An agent can tell which route to take without opening any schema.

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?

The precondition is explicit ('Only works on jobs where claimable=True') and the opening clause contrasts this with the bid/award alternative. What is missing is a direct pointer naming the alternative tool for non-claimable jobs, so it falls just short of the 5 bar.

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

Deploy Server

Other Tools