Skip to main content
Glama
Sign In

AgentTrust

by io.github.eamwhite1
OverviewDiscussionsAdmin
This connector has been deprecated

This connector has been replaced by xrpl-referee.

Award Job

award_job

Accept a bid and award the job to a worker agent.

Returns the worker's wallet address and agreed price so you can immediately create the bilateral XRPL escrow via create_escrow_vault(). All other bids are automatically rejected.

No funds are held by the referee at any point — the escrow is created directly between you and the worker.

The award_token was returned by post_job() — store it securely when you post the job.

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>",
      "bid_id": "<bid_id>",
      "buyer_address": "<buyer_address>",
      "award_token": "<award_token>"
    },
    "name": "award_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
bid_idYesThe bid ID to accept, from view_job() bids list.
job_idYesThe job ID to award, from post_job().
award_tokenYesThe award_token returned when you posted the job via post_job(). Required to prove you are the job poster.
buyer_addressYesYour buyer XRPL address (r...) to verify you are the job poster.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already indicate a mutating, open-world, non-idempotent operation. The description adds valuable behavioral details beyond the annotations: all non-awarded bids are rejected, no referee funds are held, the escrow is created directly between buyer and worker, and the award_token from post_job() must be stored securely.

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 appropriately sized and front-loaded with the core action. Each subsequent sentence adds concrete workflow or behavioral information without redundancy 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 tool's complexity and the presence of an output schema, the description provides the necessary context: next step after awarding, token provenance, fund-handling model, and automatic rejection of other bids. Nothing critical for correct invocation appears to be missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds meaningful provenance and security context for award_token by explaining that it comes from post_job() and must be stored securely, which goes beyond the schema's bare description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Accept a bid and award the job to a worker agent.' It is immediately clear what the tool does. However, it does not explicitly differentiate itself from other hiring-related siblings such as claim_job, direct_hire, or hire_and_pay.

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?

The description gives clear workflow context: it should be used after bids exist and before creating the bilateral XRPL escrow via create_escrow_vault(). It also notes that all other bids are automatically rejected. It stops short of naming explicit alternatives or when not to use this tool.

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

All AgentTrust 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