Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1

Get Escrow Info

get_escrow_info
Read-onlyIdempotent

Retrieve metadata about an existing escrow vault.

Never returns the fulfillment key — that is only returned on approval.

Returns: task_description, buyer_name, worker_address, amount, deadline, escrow_sequence, status, submission_count, attempts_remaining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
escrow_idYesThe receipt code for the vault to look up, e.g. AT-7X9K-2MQ4.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A3.9/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. The description adds that the fulfillment key is never returned, which is critical information beyond what annotations provide. It also lists the returned fields, adding transparency.

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 concise with two sentences and a list of return fields. It front-loads the key information. The list may be slightly redundant given the output schema exists, but it does not significantly waste space.

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 an output schema present, the description does not need to detail return values. It covers the main purpose and a critical behavioral constraint (no fulfillment key). For a simple read tool, this is complete enough for effective usage.

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?

Input schema coverage for escrow_id is 100% with a clear example ('e.g. AT-7X9K-2MQ4'). The description adds no additional parameter semantics; with full schema coverage, a baseline score of 3 is appropriate.

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 'Retrieve metadata about an existing escrow vault', specifying the verb and resource. It also explicitly notes what is not returned (fulfillment key), distinguishing itself from sibling tools like create_escrow_vault.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving metadata without the fulfillment key, but does not explicitly state when to use this tool over alternatives or mention any exclusions. The guidance is adequate but not explicit.

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