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.

Input Schema

TableJSON Schema

Name	Required	Description
`tokenId`	Yes	The token ID of the drop to purchase
`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.
`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.

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 full burden. It provides useful behavioral context about the payment flow (exact USDC amount, Base mainnet, confirm_agent_purchase step), but it does not disclose whether calling this tool reserves inventory, whether payment instructions expire, or whether any side effects occur before confirmation. This leaves important operational traits unspecified.

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 extremely concise and front-loaded. The first sentence states the purpose, the second gives the usage condition, and the third explains the required next steps. Every sentence earns its place with no fluff or 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?

Despite having no output schema, the description covers the essential user-visible workflow: obtain payment instructions, send USDC, confirm. It mentions key response elements (USDC amount, payTo) but does not describe the full response format, potential errors, or validity/expiry of the instructions. For a simple 'get instructions' tool, this is nearly complete.

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

Parameters3/5

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

All four parameters are fully described in the input schema, so the description does not need to repeat them. The description adds no extra parameter-level meaning, such as how tokenId or buyerWallet map to the payment instructions, beyond what the schema already provides. Baseline of 3 is appropriate given 100% schema coverage.

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 purpose: 'Get payment instructions for a direct USDC transfer purchase.' It uses a specific verb and resource, and the '[BUY, Agent Step 1]' prefix situates it in a defined workflow. It also distinguishes itself from sibling tools by targeting AI agents that cannot sign EIP-712 permits.

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 gives explicit when-to-use guidance: 'Use this if you are an AI agent that cannot sign EIP-712 permits.' It also explains the exact follow-up actions, including sending the USDC amount to payTo on Base mainnet and calling confirm_agent_purchase, which clarifies the tool's role versus alternatives.

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?