Skip to main content
Glama

Real Real Genuine

by io.github.richardjhobbs

confirm_purchase

[BUY, Step 2] Complete the purchase by submitting the signed EIP-712 permit from initiate_purchase. Mints the ERC-1155 NFT on-chain (gasless, platform covers gas) and returns a download link. 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. The response includes revenue split details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenIdYesToken ID of the listing
deadlineYesPermit deadline (Unix timestamp string from initiate_purchase)
ref_codeNoAffiliate ref code, if you are buying through another agent's product referral link. The promoter earns commission on this sale; you pay the same price.
signatureYesEIP-712 signature from wallet.signTypedData
buyerEmailNoEmail for order confirmation and file delivery. Required for physical products, buyer will not receive an order confirmation without it.
buyerWalletYesBuyer 0x wallet address
selected_sizeNoFor sized products, the size you chose at initiate_purchase. MUST match the size whose price was used to build the permit.
shipping_cityNoCity (required for physical products)
shipping_nameNoRecipient name (required for physical products)
selected_colorNoFor products with a colour axis, the colourway you chose at initiate_purchase. MUST match the colour whose price was used to build the permit; recorded on the order so fulfillment ships the right finish.
shipping_phoneNoPhone number (required for physical products, needed for delivery confirmation)
shipping_stateNoState or province
shipping_countryNoCountry (required for physical products)
shipping_postal_codeNoPostal/ZIP code (required for physical products)
shipping_address_line1NoStreet address line 1 (required for physical products)
shipping_address_line2NoStreet address line 2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions gasless minting, return of a download link, and revenue split details, but does not disclose that this is likely an irreversible financial transaction or what happens on failure. The absence of warnings about fund transfer or consequences is a notable gap.

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?

The description is concise and well-structured, with the purpose front-loaded and essential details presented in a few clear sentences. It avoids unnecessary repetition of the schema.

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?

For a complex financial tool with no output schema, the description covers key context: it references initiate_purchase, explains on-chain minting, lists physical product requirements, and mentions response contents. It could be more complete with potential error outcomes, but it is sufficiently detailed for an agent to proceed.

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?

Schema coverage is 100%, providing a baseline of 3. The description adds value by grouping and emphasizing the required fields for physical products, and explaining why shipping_phone and buyerEmail are necessary. This goes beyond the individual schema property descriptions.

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 clearly states the tool's function: 'Complete the purchase by submitting the signed EIP-712 permit from initiate_purchase' and specifies the on-chain minting of an ERC-1155 NFT. This distinguishes it from the sibling confirm_agent_purchase, which is agent-specific, by referencing the buyer's flow.

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?

The description positions this as 'Step 2' after initiate_purchase, indicating when to use it. It provides specific conditional instructions for physical products but does not explicitly contrast with confirm_agent_purchase or state when not to use it.

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 toolsInspect
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

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes with clear category tags. Minor potential confusion between get_current_brief vs list_briefs and get_brand vs get_brand_mcp_endpoint, but descriptions clarify intent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using lowercase with underscores, e.g., check_agent_standing, list_drops, submit_design. No mixing of conventions.

Tool Count3/5

32 tools is on the high side, but the server covers a wide domain including browsing, purchasing, design submission, concierge, and marketing. Each tool serves a specific function, though some consolidation could be possible.

Completeness4/5

The tool surface covers the full lifecycle of browsing, purchasing, design creation, commissions, and concierge services. Minor gaps like refund handling are absent, but the core workflows are well-supported.

Resources