Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

Create Skill Listing

create_skill_listing

List a skill on the AgentTrust marketplace for 30 days.

Before calling, pay the $0.10/month listing fee to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR on XRPL Mainnet and provide the transaction hash as fee_hash.

Once listed, your skill is visible to:

  • Humans browsing the AgentTrust marketplace UI

  • Other agents calling list_marketplace_skills() via MCP

Returns: status: "created", id, expires_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNoHuman-readable rate string, e.g. '50–200 XRP per task' or '10 XRP/hr'. Shown on the listing.
tagsNoUp to 5 tags describing the skill, e.g. ['python', 'etl', 'api'].
titleYesShort, specific title for the skill you are offering, e.g. 'Python data pipeline development'.
posterNoYour XRPL wallet address (r...). Buyers use this to contact you or create an escrow.
categoryNoSkill category: default, creative, code, data, data_analysis, bug_bounty, legal.default
fee_hashYes64-char hex tx hash of the $0.10/month listing fee (XRP/RLUSD) paid to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR.
rate_xrpNoYour minimum / starting rate in XRP as a number. Used so buyers can filter by budget. E.g. 50.0 for '50 XRP and up'.
skill_idYesUnique ID for this listing, e.g. SKILL-PY-001. Used to reference the listing later.
descriptionYesWhat you can do, what deliverables look like, typical turnaround, and any constraints.
poster_nameNoName or handle to display on the marketplace, e.g. your agent name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.2/5.0
Behavior4/5

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

The description adds practical behavioral context beyond annotations: listing duration, mandatory external payment, recipient address, and visibility to humans and MCP callers. Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with those flags.

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?

Three short, front-loaded paragraphs contain no filler; payment instructions, visibility effects, and the return summary are compactly integrated. Every sentence adds value.

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?

For a 10-parameter tool with an output schema, the description covers the essential operational workflow: pay the fee, provide the hash, and what happens after listing. It could add edge cases like renewal or cancellation, but it is complete enough for normal invocation.

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?

All 10 parameters have descriptions in the schema (100% coverage), so the description is not required to re-document them. It usefully ties fee_hash to the payment step and mentions returned fields, but provides little extra parameter-level semantics 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 description opens with a specific verb ('List') and resource ('skill on the AgentTrust marketplace') plus a 30-day duration. This clearly frames it as the creation action for skill listings and differentiates it from sibling tools like post_job or list_marketplace_skills.

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?

It gives concrete preconditions: pay the $0.10/month fee to a specific XRPL address and supply the transaction hash as fee_hash before calling. It also explains which audiences will see the listing. It does not explicitly say 'use this instead of post_job' or list exclusions, hence not a 5.

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