Skip to main content
Glama

complete_prepared_artifact_transfer

Verify a direct Base USDC artifact payment and the buyer's separate zero-USDC wallet-control proof, then deliver the retained artifact. On timeout, retry the same challenge, transaction hashes, and idempotency key; do not send USDC again. The transaction hash alone is not enough to claim a purchase. Successful delivery includes exact delivery.bodyBase64 bytes and private delivery.artifactProof for commitment verification.

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": {
      "merchantId": "<merchantId>",
      "offerId": "<offerId>",
      "payer": "<payer>",
      "challengeId": "<challengeId>",
      "method": "<method>",
      "identityTransactionHash": "<identityTransactionHash>",
      "paymentTransactionHash": "<paymentTransactionHash>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "complete_prepared_artifact_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
payerYes
methodYes
offerIdYes
merchantIdYes
challengeIdYes
idempotencyKeyYes
paymentTransactionHashYes
identityTransactionHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does disclose the highest-risk behavior: idempotent replay on timeout, the prohibition on re-sending USDC, and that hashes alone don't prove purchase. It also describes the successful response's private fields (delivery.bodyBase64, delivery.artifactProof) despite having no output schema. It doesn't cover authentication requirements, failure/partial-verification outcomes, or whether the artifact is released on repeated calls.

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?

Four sentences, front-loaded with the purpose before the retry caveat and the return-value note. The caveat 'The transaction hash alone is not enough to claim a purchase' earns its place as a guardrail. Some density of protocol jargon slightly reduces immediate readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-required-parameter payment-verification tool with no annotations and no output schema, the description covers the happy path and the timeout path reasonably. It leaves gaps around failure semantics (verification mismatch, expired challenge, wrong payer) and around what happens to the retained artifact if completion is never called.

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

Parameters2/5

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

Schema description coverage is 0% across 8 required parameters, so the description must compensate. It does clarify that the challenge id, both transaction hashes, and the idempotency key refer to the same prior attempt, and it implicitly distinguishes the payment hash from the identity/wallet-control hash, but payer, merchantId, offerId, and the approve_zero vs transfer_zero method enum are given no meaning at all.

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 opens with a specific verb and object: 'Verify a direct Base USDC artifact payment and the buyer's separate zero-USDC wallet-control proof, then deliver the retained artifact.' It names both verification inputs (payment + wallet-control proof) and the side effect (delivery), which distinguishes it from the challenge-creation and purchase siblings without needing their schemas.

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?

It states the entry condition (a payment and a separate control proof must already exist) and gives explicit retry guidance: on timeout, reuse the same challenge, hashes, and idempotency key and do not send USDC again. It also warns that a transaction hash alone is insufficient. It stops short of naming a specific alternative tool for the payment-creation step or saying what to do when verification fails.

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.

Resources