Real Real Genuine

confirm_agent_purchase

[BUY, Agent Step 2] Confirm your USDC payment and claim the listing. Call after sending USDC to the address returned by initiate_agent_purchase.

Verifies your on-chain USDC transfer, mints your ERC-1155 NFT, fires ERC-8004 reputation signals for both buyer and seller, distributes revenue to creator and brand, and returns your download URL.

Include buyerAgentId (your ERC-8004 agent ID) for an agent-to-agent trust signal on-chain.

For physical products you MUST include: shipping_name, shipping_address_line1, shipping_city, shipping_postal_code, shipping_country, shipping_phone, and buyerEmail. shipping_phone is required for delivery confirmation. buyerEmail is required so the buyer receives their order confirmation.

Input Schema

TableJSON Schema

Name	Required	Description
`txHash`	Yes	Your USDC transfer transaction hash on Base
`tokenId`	Yes	The listing token ID
`buyerEmail`	No	Email address for order confirmation and file delivery. Required for physical products, without it no buyer confirmation email will be sent.
`buyerWallet`	Yes	Your wallet address
`buyerAgentId`	No	Your ERC-8004 agent ID for on-chain reputation signals (e.g. 17666)
`selected_size`	No	For sized products, the size you chose at initiate_agent_purchase. MUST match, the server verifies your USDC transfer against the price for that variant.
`shipping_city`	No	City (required for physical products)
`shipping_name`	No	Recipient name (required for physical products)
`selected_color`	No	For products with a colour axis, the colourway you chose at initiate_agent_purchase. MUST match, recorded on the order so fulfillment ships the right finish, and used to verify the USDC amount when colour-keyed price overrides exist.
`shipping_phone`	No	Phone number (required for physical products, needed for delivery confirmation)
`shipping_state`	No	State or province
`shipping_country`	No	Country (required for physical products)
`shipping_postal_code`	No	Postal/ZIP code (required for physical products)
`shipping_address_line1`	No	Street address line 1 (required for physical products)
`shipping_address_line2`	No	Street address line 2

TDQS

A4.5/5.0

Behavior4/5

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

There are no annotations, so the description carries the full burden of disclosing side effects. It does so thoroughly: verifies the on-chain transfer, mints an ERC-1155 NFT, fires ERC-8004 reputation signals, distributes revenue, and returns a download URL. It also highlights the need for buyerAgentId for trust signals. However, it does not cover failure modes, reversibility, or idempotency, which would make it 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?

The description is slightly long but well-structured: it opens with a bracketed step label, states the purpose, then sequentially covers the call precondition, the effects, and special parameter requirements. Every sentence adds useful information, and the structure makes it scannable. It earns a 4, not a 5, because the physical-product field list is repeated from the schema, adding minor redundancy.

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?

Given the complexity (15 parameters, no output schema, no annotations), the description covers the essential operational context: the trigger condition, the sequence of on-chain effects, and the return of a download URL. It also specifies which parameters are mandatory for physical goods. It does not describe error scenarios or the exact result schema beyond the URL, but it is sufficiently complete for an agent to invoke the tool correctly.

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?

The input schema already covers 100% of parameters with descriptions, so the baseline is 3. The description adds meaningful value beyond the schema by clarifying relationships: selected_size and selected_color must match the initiate call, buyerAgentId is for on-chain trust, and the physical-product required fields are grouped. This elevates the score above baseline.

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 states a clear, specific purpose: 'Confirm your USDC payment and claim the listing.' It lists concrete actions (verifies transfer, mints NFT, fires reputation signals, distributes revenue, returns download URL) and explicitly identifies this as 'Agent Step 2' with a referenced prerequisite tool (initiate_agent_purchase), distinguishing it from sibling tools like confirm_purchase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: 'Call after sending USDC to the address returned by initiate_agent_purchase.' It also gives conditional instructions for physical products (mandatory fields) and explains why certain fields are required (e.g., shipping_phone for delivery confirmation, buyerEmail for order confirmation). This clearly situates the tool in a multi-step workflow.

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

All Real Real Genuine tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation3/5

Several tool pairs could be confused, such as get_offers vs get_redemption_offers, get_world_eggs vs discover_egg, and the human vs agent purchase flows (initiate_purchase/confirm_purchase vs initiate_agent_purchase/confirm_agent_purchase). The descriptions are detailed and mostly disambiguating, but the presence of a retired tool (create_concierge) and multiple similarly named status/check tools add ambiguity.

Naming Consistency4/5

The vast majority of tools follow a snake_case verb_noun pattern (list_drops, submit_design, redeem_points, verify_world_id). Minor deviations include 'priscilla_post' (proper noun prefix) and the interchangeable use of get/check/verify for status-like tools, but the overall convention is consistent and readable.

Tool Count2/5

With 44 tools, the server is well above the 25-tool threshold that makes a surface feel heavy. Even though the platform covers many domains (commerce, affiliate, design, quests, concierge, marketing), this many tools strains discoverability and agent decision-making.

Completeness2/5

The buyer and designer flows are well covered (search → detail → purchase → download; brief → submit → status), but the brand side is incomplete. register_brand promises the ability to create briefs and product listings, yet no tools exist to create briefs or products, and there are no update/delete/refund operations for any resource, leaving registered brands at a dead end.

Resources

Need Help?