Skip to main content
Glama

Assess Counterparty and Job

assess_counterparty_and_job
Read-onlyIdempotent

Single pre-flight check before locking funds in escrow.

Aggregates trust score, sanctions, KYC, NFT issuer registry, domain status, recommended release conditions, suggested escrow cap, and go/no-go rules — in one call. Run this before create_escrow_vault or hire_and_pay.

Returns a structured report with a top-level 'proceed' bool and a 'do_not_proceed_if' list of triggered blockers. If proceed is False, do not lock funds.

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": {
      "worker_address": "<worker_address>"
    },
    "name": "assess_counterparty_and_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNo'mainnet' (default), 'testnet', or 'auto' (tries mainnet then testnet if not found). Testnet wallets pass proceed:true even with low scores.auto
job_typeNoNatural-language description of the work — e.g. 'software development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend release conditions.general
amount_xrpNoHow much XRP you plan to lock in escrow. Used to check whether the counterparty's KYC level allows it.
worker_addressYesThe XRPL wallet address of the counterparty you are considering hiring or paying.
nft_issuer_queryNoIf the job involves an NFT proof, pass the issuer name or wallet address to check the registry.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / network
      Added value: +{
      +  "default": "auto",
      +  "description": "'mainnet' (default), 'testnet', or 'auto' (tries mainnet then testnet if not found). Testnet wallets pass proceed:true even with low scores.",
      +  "enum": [
      +    "mainnet",
      +    "testnet",
      +    "auto"
      +  ],
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / amount_xrp / title
      Added value: +"Intended Escrow Amount (XRP)"
    • addedInput schema / properties / nft_issuer_query / title
      Added value: +"NFT Issuer Name or Wallet (optional)"
    • addedInput schema / properties / worker_address / title
      Added value: +"Worker XRPL Wallet Address"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world, so the description is not carrying the safety burden alone. It still adds real value by describing the return contract (top-level 'proceed' bool plus a 'do_not_proceed_if' blocker list) and an explicit action rule — do not lock funds when proceed is False — which no structured field conveys.

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-loaded with the core purpose, then the aggregation list, then the return shape, then the action rule — a logical escalation with no filler. The slight repetition of the pre-flight framing is minor and serves emphasis.

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?

For a five-parameter aggregate tool with full schema coverage and an output schema, this covers everything an agent needs: what it checks, when to call it, what it returns, and how to act on the result. No gaps remain against the surrounding structured data.

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 description coverage is 100%, including enum values, defaults, and per-field purposes, so the schema does the heavy lifting. The description adds only the aggregate notion that inputs feed a combined assessment, not any new per-parameter semantics; baseline 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?

States a specific verb and composite resource: a single pre-flight assessment that aggregates trust score, sanctions, KYC, NFT issuer registry, domain status, and release conditions. This clearly distinguishes it from the granular siblings it composes (get_wallet_trust_score, check_wallet_sanctions, check_wallet_kyc).

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?

'Run this before create_escrow_vault or hire_and_pay' gives an explicit trigger point and names the downstream tools it gates. It does not say when to skip this tool in favor of the individual component checks, so it stops just short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.