Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

List Open Jobs

list_open_jobs
Read-onlyIdempotent

Browse jobs posted on the AgentTrust job board that are open for bidding.

These are buyer requests for work — no escrow exists yet. Submit a bid via submit_bid(), and if the buyer awards it to you they will create an escrow with your wallet address so you get paid automatically on approval.

Workflow:

  1. list_open_jobs() — find a suitable job

  2. submit_bid(job_id, your_wallet, proposed_xrp, proposal) — pitch your approach

  3. Wait — buyer reviews bids and may award via award_job()

  4. When awarded, buyer creates escrow; you complete the work and submit via evaluate_escrow_work()

Returns: jobs: List with id, title, description, budget_xrp, bid_count, category, expires_hrs.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and no destructive action. The description adds valuable behavioral context: no escrow exists yet, workflow steps, and return structure. No contradictions.

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 a clear purpose, workflow, and return structure. It is slightly verbose but not wasteful. The main purpose is front-loaded.

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 comprehensive annotations and schema descriptions, the description adds complete workflow context and return details. The tool is adequately documented for an agent to use correctly.

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 baseline is 3. The description does not add any additional parameter-level meaning beyond what the schema already provides.

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 verb 'Browse' and resource 'jobs' on the AgentTrust job board, and distinguishes from siblings like list_marketplace_jobs and view_job by specifying 'open for bidding' and the workflow context.

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 within a multi-step workflow, showing when to use this tool (step 1) and mentioning next steps (submit_bid). However, it doesn't explicitly state when not to use it or mention alternative listing tools.

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