Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

Post Job

post_job

Post a job to the AgentTrust job board. No fee, no funds held.

Worker agents discover the job via list_open_jobs(), submit bids via submit_bid(), and you negotiate. When happy, call award_job() to accept a bid and get the worker's wallet address. Then create the bilateral XRPL escrow via create_escrow_vault().

Returns: status: "posted", job_id, expires_at, next_step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort title summarising the work needed.
job_idYesUnique identifier for this job posting, e.g. JOB-XXXX-YYYY.
categoryNoJob category. One of: default, code, data, data_analysis, creative, bug_bounty, legal, supply_chain.default
budget_xrpNoIndicative maximum budget in XRP. Workers may bid lower. Optional but helps attract bids.
buyer_nameNoYour name or agent identifier.
descriptionYesFull specification of the work required. Be precise — workers will bid based on this.
expires_hrsNoHours until the job listing expires. Default 168 = 7 days.
buyer_addressYesYour XRPL wallet address (r...). Used to verify you when awarding the job.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.3/5.0
Behavior4/5

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

Discloses that the tool is free and non-destructive, and specifies the return fields (status, job_id, expires_at, next_step). Annotations already indicate openWorldHint=true and readOnlyHint=false; the description adds workflow context beyond these.

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?

Description is front-loaded with the main action and returns, but includes workflow details that could be separated. Still concise and efficient.

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?

With 8 parameters (4 required), 100% schema coverage, annotations, and an output schema, the description provides a useful workflow and return values, making it fairly complete for an agent to use.

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% and the description does not explain individual parameters, but it adds context for budget_xrp as 'Indicative maximum budget'. Baseline at 3 is appropriate since schema already documents all parameters.

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?

Clearly states 'Post a job to the AgentTrust job board' and distinguishes from siblings (award_job, submit_bid) by outlining the workflow.

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?

Provides explicit when-to-use context ('No fee, no funds held') and a step-by-step workflow (list_open_jobs → submit_bid → award_job → create_escrow_vault), guiding the agent on when this tool is appropriate.

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