Skip to main content
Glama

create_prepared_artifact_transfer_challenge

Prepare a noncustodial direct-USDC checkout for a prepared artifact. Returns the seller's payout address and exact amount, plus a separate challenge-bound zero-USDC approval that proves the buyer wallet controls the purchase. Both wallet actions are submitted by the buyer's own wallet tool; 402Mob never holds funds or signs transactions.

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>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_prepared_artifact_transfer_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
payerYes
offerIdYes
merchantIdYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the return payload (seller payout address and exact amount, plus a zero-USDC approval), the custody model (402Mob never holds funds or signs transactions), and that wallet actions happen outside this call. It omits idempotency semantics, challenge expiry, and failure behavior, which keeps it below a 5.

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?

Three sentences, front-loaded with the core action and then the return value and the noncustodial guarantee. Every sentence carries information; only the custody sentence is somewhat defensive but still relevant to agent trust.

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?

Because there is no output schema, the description usefully spells out the returned values and the external wallet steps. It still leaves the agent guessing about idempotencyKey behavior, challenge lifetime, and which sibling completes the flow, so it is adequate but not complete for a four-parameter mutation-adjacent tool.

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 four required parameters, and the description never mentions merchantId, offerId, payer, or idempotencyKey. The role of a buyer wallet ('proves the buyer wallet controls the purchase') and of a prepared artifact/offer is loosely implied, but nothing explains the UUID/address formats or what the idempotencyKey governs, so the compensation gap is substantial.

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 names a specific verb+resource ('Prepare a noncustodial direct-USDC checkout for a prepared artifact') and explains what the call produces. It does not name the sibling tools that consume its output (e.g. complete_prepared_artifact_transfer) or distinguish itself from buy_prepared_artifact, so sibling differentiation is only implicit.

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?

Usage is implied by the sequence described ('Both wallet actions are submitted by the buyer's own wallet tool'), which tells an agent this is a preparation step that precedes wallet signing. However, there is no explicit when-to-use/when-not statement and no alternative named, so the agent must infer that this is the first step rather than a substitute for the buy/complete tools.

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