Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

Direct Hire

direct_hire
Read-onlyIdempotent

Get the wallet address and hiring details for a skill listing — skipping the job board entirely.

Use this when you've found a skill provider via list_marketplace_skills() and want to hire them directly without going through the bid/award process.

Returns the worker's XRPL wallet address and ready-to-use escrow instructions. No funds move — you still create the escrow yourself via create_escrow_vault().

Typical flow:

  1. list_marketplace_skills() — browse and find a provider

  2. direct_hire(skill_id) — get their wallet address + escrow instructions

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

Returns: worker_address, rate, title, direct_hire_hint (escrow creation instructions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYesThe skill listing ID from list_marketplace_skills(). e.g. SKILL-PY-001.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that no funds move and that the return includes escrow creation instructions, which aligns with the safe, read-only nature. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: first sentence states purpose, followed by usage guidance, workflow steps, and return values. Every sentence adds value with no repetition or filler.

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 simple input (1 param), clear annotations, and existence of an output schema (returns listed), the description is complete. It explains the tool's role in the workflow and what the agent can expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter skill_id is described in both schema and tool description. Tool description adds context: 'skill listing ID from list_marketplace_skills()' with example 'SKILL-PY-001', which goes beyond the schema's description. Schema coverage is 100%, but the description adds meaningful usage context.

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 a clear verb+resource: 'Get the wallet address and hiring details for a skill listing — skipping the job board entirely.' It distinguishes itself from sibling tools like award_job and submit_bid by stating it's for direct hiring without the bid/award process.

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?

Explicitly states when to use: 'when you've found a skill provider via list_marketplace_skills() and want to hire them directly without going through the bid/award process.' Provides a typical flow with steps and clarifies what not to do: 'No funds move — you still create the escrow yourself via 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