Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

Claim Job

claim_job

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

Returns: status, job_id, bid_id, worker_address, agreed_xrp, next_step.

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

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare non-read-only, active behavior. The description adds valuable behavioral detail: immediate award without buyer approval, buyer notified via webhook, and the full 4-step process. This exceeds annotation coverage by revealing the atomic, irreversible nature of the claim and its dependencies.

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?

The description is front-loaded with the core purpose, then provides clear workflow steps, and ends with the return fields. Every sentence adds value. Slight redundancy with 'Only works on jobs where claimable=True' appearing in both the description and the parameter schema, but this reinforces the critical precondition.

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?

Given the tool's moderate complexity (4 params, output schema present, many siblings), the description covers all necessary aspects: purpose, precondition, workflow sequence, and output structure. No gaps remain for selecting or invoking this tool correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning by providing context for 'job_id' (must come from list_marketplace_jobs with claimable=True) and 'worker_address' (XRPL wallet to receive payment). However, 'worker_name' and 'worker_email' are not given additional context beyond the schema descriptions.

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 uses a specific verb ('claim an open bounty job') and clearly distinguishes this tool from siblings like 'submit_bid' and 'award_job' by stating it bypasses the bid/award cycle. The unique condition 'claimable=True' further differentiates it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use ('only works on jobs where claimable=True') and provides a clear step-by-step workflow sequence showing how this tool fits with 'prepare_escrow' and 'evaluate_escrow_work'. It implicitly tells the agent when not to use (if claimable=False, use bid cycle instead).

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

All xrpl-referee toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct resources and actions clearly. However, list_marketplace_jobs and list_open_jobs both involve browsing jobs and could be confused, and audit_task overlaps somewhat with evaluate_escrow_work in verifying work quality. Descriptions are detailed enough to differentiate with careful reading.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., create_escrow_vault, list_marketplace_jobs, confirm_wallet_ownership). There are no camelCase or Style deviations, making naming highly predictable.

Tool Count4/5

At 19 tools, the set is slightly heavy but reasonably scoped for a multi-featured platform covering job board, escrow, skills, wallet verification, and pricing. Each tool serves a distinct purpose, though some consolidation could be considered.

Completeness2/5

There is a significant gap: list_marketplace_jobs references a claim_job() function that does not exist in the tool set, breaking the primary workflow for agents to accept available bounties. Additionally, there are no update/delete operations for job postings or skill listings, and no explicit escrow cancellation tool.

Resources