Skip to main content
Glama
Sign In
AgentTrust

AgentTrust

by eamwhite1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Confirm Wallet Ownership

confirm_wallet_ownership

Complete wallet ownership verification using the XRPL AccountSet transaction you broadcast.

Instructions

Complete wallet ownership verification using the XRPL AccountSet transaction you broadcast.

Looks up the tx on-chain, confirms it came from the claimed wallet, and verifies the Memo contains the expected challenge. On success, a WalletVerification record is stored and the wallet earns +8 points on its trust score.

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": {
      "wallet_address": "<wallet_address>",
      "tx_hash": "<tx_hash>"
    },
    "name": "confirm_wallet_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashYesThe XRPL transaction hash of the AccountSet tx you submitted with the challenge in a Memo.
issuer_idNoIf you are verifying ownership for an NFT issuer registry entry, provide its ID to mark it verified.
wallet_addressYesThe XRPL wallet address (r...) you are verifying.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.1.0
    • addedInput schema / properties / issuer_id / title
      Added value: +"Issuer ID (optional)"
    • addedInput schema / properties / tx_hash / title
      Added value: +"Transaction Hash"
    • addedInput schema / properties / wallet_address / title
      Added value: +"XRPL Wallet Address"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations mark this non-read-only, non-idempotent and non-destructive, but give no detail; the description fills that gap by disclosing the on-chain lookup, source check, memo validation, that a WalletVerification record is written, and the +8 trust-score reward. It stops short of describing failure modes (bad memo, reused tx) or why repeat calls are non-idempotent.

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?

Two tight sentences: the first names the operation and its input, the second walks the verification pipeline and outcome. Every clause carries information and the outcome is front-loaded.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers the flow and persisted side effect well. The remaining gap is sequencing — the agent must infer that a challenge and broadcast precede this call — and unstated behavior on verification failure.

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%, so all three parameters, including the optional issuer_id, are already documented in the schema. The description alludes to the tx and wallet but adds no format or constraint detail beyond what the schema states.

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 ('Complete wallet ownership verification') and pins the mechanism ('XRPL AccountSet transaction'). It is clearly distinguishable from nearby siblings like verify_wallet_domain, verify_nft_ownership, and check_wallet_kyc because it names the AccountSet/memo challenge path.

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 phrase 'using the ... transaction you broadcast' implies the prerequisite that a challenge was already obtained and a tx submitted (presumably via get_wallet_verification_challenge), but the sibling is never named. There is no explicit when-not-to-use or statement of what to do if no tx has been broadcast yet.

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

Deploy Server

Other Tools