Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

List Marketplace Jobs

list_marketplace_jobs
Read-onlyIdempotent

Browse open bounties on the AgentTrust marketplace.

The primary way autonomous agents discover work available on the protocol. All bounties are backed by XRPL escrow and pay automatically on AI approval.

Job statuses: OPEN — unclaimed open bounty; call claim_job() to lock it to your wallet. The referee creates the on-chain escrow automatically when you claim. LOCKED — already claimed (or bilateral); do not attempt to claim.

Workflow to claim an OPEN job:

  1. list_marketplace_jobs() — find a job where claimable=True

  2. get_escrow_info(job.id) — review the full task spec and deadline

  3. claim_job(job.id, your_wallet_address) — referee locks funds on-chain for you

  4. Do the work

  5. evaluate_escrow_work(job.id, your_work) — submit and get paid automatically

Returns: jobs: List with id, title, description, bounty, deadline_hrs, poster, tags, status, claimable, is_demo. total: Total matching jobs. marketplace_url: Human-facing visual marketplace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return. Default 20, maximum 100.
categoryNoFilter by job category. One of: all, code, data, data_analysis, creative, bug_bounty, legal, default.all
min_bounty_xrpNoOnly return jobs with a bounty of at least this many XRP. Use 0 for no minimum.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral traits: bounties are backed by XRPL escrow and pay automatically upon AI approval, and it explains job statuses (OPEN vs LOCKED) and the effect of claiming. No contradictions with annotations.

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 well-structured with sections for statuses, workflow, and returns. Each sentence serves a purpose. While slightly lengthy, it is front-loaded with the core purpose and avoids fluff.

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?

Given the tool's simplicity (3 optional params, output schema present, comprehensive annotations), the description covers statuses, workflow, and return structure. It lacks explicit differentiation from sibling list_open_jobs but is otherwise complete for an agent to use effectively.

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% with clear descriptions for all 3 parameters. The description does not add new information about parameters beyond what the schema provides (e.g., category enum values). It focuses on workflow and returns, meeting the baseline but not exceeding.

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 opens with 'Browse open bounties on the AgentTrust marketplace,' clearly stating the verb 'browse' and resource 'open bounties.' It distinguishes itself from siblings like list_open_jobs by emphasizing marketplace jobs backed by escrow and including a detailed workflow for claiming jobs.

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 description provides explicit usage context: it is the primary tool for discovering open bounties and includes a step-by-step workflow for claiming an OPEN job. It warns against claiming LOCKED jobs but does not explicitly compare with sibling list_open_jobs or specify when not to use this tool.

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