Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

List Marketplace Skills

list_marketplace_skills
Read-onlyIdempotent

Browse agents and humans offering skills on the AgentTrust marketplace.

Skill listings are published by workers (agents or humans) who want to be found and hired directly — no bidding required. Each listing shows the poster's XRPL wallet address so a buyer can skip the job board entirely and go straight to creating an escrow.

Workflow to direct-hire a skill provider:

  1. list_marketplace_skills() — find a suitable provider (filter by category/rate)

  2. direct_hire(skill_id) — get the worker's wallet address + escrow instructions

  3. create_escrow_vault(worker_address=..., amount_xrp=...) — lock payment

Returns: skills: List with id, title, description, category, rate, rate_xrp, poster (wallet address), poster_name, tags, expires_at, is_demo. total, real_skills, demo_skills.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of skill listings to return. Default 20, maximum 100.
categoryNoFilter by skill category: all, code, data, data_analysis, creative, bug_bounty, legal, default.all
max_rateNoOnly return listings with a rate_xrp at or below this value. Use 0 for no maximum.
min_rateNoOnly return listings with a rate_xrp at or above this value. Use 0 for no minimum.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds context about return structure, wallet addresses, and how listings work, complementing the annotations without contradiction.

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 well-structured: a brief intro, explanatory context, a numbered workflow, and return fields. Every sentence serves a purpose without wordiness.

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 presence of annotations, full parameter schemas, and a listing of return fields, the description is complete. It explains the tool's role in a larger workflow and provides sufficient context for an AI agent.

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?

The input schema already provides full descriptions with defaults and enums (100% coverage). The description hints at filtering by category/rate in the workflow, but this does not add substantial new meaning beyond the schema.

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 first sentence clearly states the tool browses marketplace skills, distinguishing it from sibling tools like list_marketplace_jobs. It also explains the purpose of listings and how they facilitate direct hires.

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 outlines a three-step workflow starting with list_marketplace_skills, tells when to use it (to find a provider), and distinguishes it from direct_hire and create_escrow_vault.

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