Skip to main content
Glama
Sign In

AgentTrust XRPL

by io.github.eamwhite1
OverviewDiscussionsAdmin

View Job

view_job
Read-onlyIdempotent

View a job posting and all current bids.

Use this to check the status of a job you posted or bid on. If status is 'awarded', awarded_bid_id shows the winning bid. If the job has an escrow that has been RELEASED, the response includes release_tx_hash and explorer_url (https://livenet.xrpl.org/transactions/) so you can verify payment on-chain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "view_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job ID to view, from list_open_jobs() or post_job().

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / job_id / title
      Added value: +"Job ID"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description earns credit by disclosing conditional response behavior: awarded_bid_id on 'awarded' status and release_tx_hash/explorer_url when escrow is RELEASED, with the URL format — details annotations cannot express.

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?

Front-loads the core action in one sentence, then adds only decision-relevant conditionals. No filler; each sentence carries distinct information.

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?

An output schema exists, yet the description still adds the conditional logic linking status to awarded_bid_id and escrow release to on-chain verification fields. Nothing an agent needs to interpret the response is missing.

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 job_id is fully documented in the schema, including where to obtain it. The description adds no further parameter semantics, so the baseline 3 applies.

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?

States a specific verb and resource ('View a job posting and all current bids'), which cleanly separates it from the list_* siblings that enumerate jobs. An agent can tell this is the single-job detail view without opening the schema.

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?

'Use this to check the status of a job you posted or bid on' gives a clear usage context and implies the read-a-single-job scenario. It doesn't explicitly name a competing alternative or exclusion (e.g., vs. list_open_jobs), which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentTrust XRPL toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources