Real Real Genuine

initiate_agent_purchase

[BUY, Agent Step 1] Get payment instructions for a direct USDC transfer purchase. Use this if you are an AI agent that cannot sign EIP-712 permits.

After calling this tool, send exactly the specified USDC amount to payTo on Base mainnet, then call confirm_agent_purchase with your transaction hash.

PHYSICAL PRODUCTS: the amount includes shipping. Pass the delivery address; if you omit shipping_rate_handle the tool returns the live shipping options (in USDC) for that address instead of payment instructions. Call again with the handle you chose. Pass the same address and handle to confirm_agent_purchase, the server re-quotes them at settlement.

Input Schema

Name	Required	Description
`tokenId`	Yes	The token ID of the drop to purchase
`buyerEmail`	No	Email for the order confirmation. Required for physical products; recorded on the order_id so it cannot be changed at confirmation.
`buyerWallet`	Yes	Your wallet address on Base
`selected_size`	No	For sized products (e.g. sneakers, garments), the size you want to buy (e.g. "10.5", "M"). Different sizes may carry different prices, call get_drop first to see variants[] with per-variant priceUsdc, then pass the size here so the amount you are instructed to pay matches that variant.
`shipping_city`	No	City (required for physical products)
`shipping_name`	No	Recipient name (physical products)
`selected_color`	No	For products with a colour axis (e.g. a filtered showerhead in five finishes), the colourway you want to buy. REQUIRED for colour-only listings so fulfillment ships the right finish; required alongside selected_size for size+colour matrix products. Inspect variants[] from get_drop_details to see available colours.
`shipping_phone`	No	Phone number for the carrier
`shipping_state`	No	State / province code (required for US, CA, AU)
`shipping_country`	No	ISO 3166-1 alpha-2 country code, e.g. "GB" (required for physical products)
`shipping_postal_code`	No	Postal / ZIP code (required for physical products)
`shipping_rate_handle`	No	Handle of the shipping option you chose from a previous call. Omit to list the options for the address.
`shipping_address_line1`	No	Street address line 1 (required for physical products)
`shipping_address_line2`	No	Street address line 2

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / buyerEmail

Added value: +{
+  "description": "Email for the order confirmation. Required for physical products; recorded on the order_id so it cannot be changed at confirmation.",
+  "format": "email",
+  "type": "string"
+}

Changed9 schema fields changedSep 20, 2026

addedInput schema / properties / shipping_address_line1

Added value: +{
+  "description": "Street address line 1 (required for physical products)",
+  "type": "string"
+}

addedInput schema / properties / shipping_address_line2

Added value: +{
+  "description": "Street address line 2",
+  "type": "string"
+}

addedInput schema / properties / shipping_city

Added value: +{
+  "description": "City (required for physical products)",
+  "type": "string"
+}

addedInput schema / properties / shipping_country

Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code, e.g. \"GB\" (required for physical products)",
+  "type": "string"
+}

addedInput schema / properties / shipping_name

Added value: +{
+  "description": "Recipient name (physical products)",
+  "type": "string"
+}

addedInput schema / properties / shipping_phone

Added value: +{
+  "description": "Phone number for the carrier",
+  "type": "string"
+}

addedInput schema / properties / shipping_postal_code

Added value: +{
+  "description": "Postal / ZIP code (required for physical products)",
+  "type": "string"
+}

addedInput schema / properties / shipping_rate_handle

Added value: +{
+  "description": "Handle of the shipping option you chose from a previous call. Omit to list the options for the address.",
+  "type": "string"
+}

addedInput schema / properties / shipping_state

Added value: +{
+  "description": "State / province code (required for US, CA, AU)",
+  "type": "string"
+}

Changed1 schema field changedJun 2, 2026

changedInput schema / properties / selected_size / description

Previous value: -"For sized products (e.g. sneakers, garments), the size you want to buy (e.g. \"10.5\", \"M\"). Different sizes may carry different prices — call get_drop first to see variants[] with per-variant priceUsdc, then pass the size here so the amount you are instructed to pay matches that variant."New value: +"For sized products (e.g. sneakers, garments), the size you want to buy (e.g. \"10.5\", \"M\"). Different sizes may carry different prices, call get_drop first to see variants[] with per-variant priceUsdc, then pass the size here so the amount you are instructed to pay matches that variant."

Changed2 schema fields changedMay 4, 2026

addedInput schema / properties / selected_color

Added value: +{
+  "description": "For products with a colour axis (e.g. a filtered showerhead in five finishes), the colourway you want to buy. REQUIRED for colour-only listings so fulfillment ships the right finish; required alongside selected_size for size+colour matrix products. Inspect variants[] from get_drop_details to see available colours.",
+  "type": "string"
+}

changedInput schema / properties / selected_size / description

Previous value: -"For sized products (e.g. sneakers, garments), the size you want to buy (e.g. \"10.5\", \"M\"). Different sizes may carry different prices — call get_drop first to see variants[] with per-size priceUsdc, then pass the size here so the amount you are instructed to pay matches that size."New value: +"For sized products (e.g. sneakers, garments), the size you want to buy (e.g. \"10.5\", \"M\"). Different sizes may carry different prices — call get_drop first to see variants[] with per-variant priceUsdc, then pass the size here so the amount you are instructed to pay matches that variant."

Changed1 schema field changedApr 23, 2026

addedInput schema / properties / selected_size

Added value: +{
+  "description": "For sized products (e.g. sneakers, garments), the size you want to buy (e.g. \"10.5\", \"M\"). Different sizes may carry different prices — call get_drop first to see variants[] with per-size priceUsdc, then pass the size here so the amount you are instructed to pay matches that size.",
+  "type": "string"
+}

First observedMar 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses the two-step pay-then-confirm flow, the exact payment target (payTo on Base mainnet), the branch where omitting shipping_rate_handle yields live shipping options instead of instructions, and that the server re-quotes address/handle at settlement. It omits failure modes such as instruction expiry or what happens if the wrong amount is sent.

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?

Front-loaded with a bracketed role/step tag, then the core flow, then a clearly separated PHYSICAL PRODUCTS section. It is dense for a 14-parameter multi-step tool but every sentence conveys distinct operational information; only minor tightening is possible.

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?

There is no output schema and no annotations, so the description must cover both behavior and the shape of what comes back; it adequately explains the primary return (payment instructions vs. shipping options) and the required downstream call. Minor gaps remain around error and expiry handling for a payment flow.

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 description coverage is 100%, so the schema already documents all 14 parameters and the baseline is 3. The description adds genuine value beyond the schema by explaining the conditional semantics of shipping_rate_handle (omit to list options) and the re-quote-at-settlement behavior tied to address and handle.

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 tag '[BUY, Agent Step 1] Get payment instructions for a direct USDC transfer purchase' states a specific verb and resource, and the audience condition ('AI agent that cannot sign EIP-712 permits') distinguishes it from the sibling initiate_purchase flow. An agent can tell from the text alone which purchase-initiation path applies to it.

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 gives an explicit selection condition (use this if you cannot sign EIP-712 permits) and a clear follow-up step (send USDC, then call confirm_agent_purchase). It never names the alternative initiate_purchase tool by name, so routing is inferred rather than stated, but the context is unambiguous.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

initiate_agent_purchase

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources