AZPay Monetize — Sepolia Sandbox

Prepare checkout

prepare_checkout

Use this after an accepted offer to review the amount and get a single-use confirmation. Use pay_and_access to spend; this tool never pays. Input: offer_id, or resource_id with optional quantity for the list price. Returns the checkout summary, confirmation, total, and expiry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_checkout"
  }
}

Input Schema

Name	Required	Description
`offer_id`	No	Accepted offer id from negotiate_price. Omit it only when passing resource_id for the list price.
`quantity`	No	Optional quantity for a list-price checkout, from 1 to 100. Defaults to 1.
`resource_id`	No	Resource id, used to prepare the list price when you have no offer_id.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`paid`	Yes
`payee`	Yes
`network`	Yes
`options`	Yes
`payment`	Yes
`testnet`	Yes
`offer_id`	Yes
`quantity`	Yes
`resource`	Yes
`expires_at`	Yes
`total_usdc`	Yes
`transaction`	Yes
`confirmation`	Yes
`instructions`	Yes
`network_name`	Yes
`schema_version`	Yes
`uses_remaining`	Yes
`expires_at_europe_madrid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 9, 2026

removedInput schema / properties / id

Removed value: -{
-  "description": "Deprecated alias of resource_id.",
-  "maxLength": 120,
-  "type": "string"
-}

removedInput schema / properties / oferta

Removed value: -{
-  "description": "Deprecated alias of offer_id.",
-  "maxLength": 80,
-  "type": "string"
-}

changedInput schema / properties / offer_id / description

Previous value: -"Accepted offer id."New value: +"Accepted offer id from negotiate_price. Omit it only when passing resource_id for the list price."

removedInput schema / properties / quantidade

Removed value: -{
-  "description": "Deprecated alias of quantity.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

changedInput schema / properties / quantity / description

Previous value: -"Quantity for a direct purchase, from 1 to 100."New value: +"Optional quantity for a list-price checkout, from 1 to 100. Defaults to 1."

changedInput schema / properties / resource_id / description

Previous value: -"Resource id, to prepare the list price without negotiating."New value: +"Resource id, used to prepare the list price when you have no offer_id."

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnly=false, destructive=false, openWorld=false, and the description adds substantive context beyond that: the tool creates a single-use confirmation that expires but never moves money. What is missing is whether repeated calls are idempotent or how long the confirmation stays valid, which matters for a non-destructive but state-creating call.

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?

Three tight sentences, front-loaded with the trigger condition, then the sibling boundary, then inputs and returns. Nothing is padded; each clause carries a distinct decision-relevant fact.

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?

With an output schema present, the description wisely only summarizes returns (summary, confirmation, total, expiry) and instead spends its budget on preconditions and the no-payment guarantee. It does not note that no parameter is strictly required or how confirmation lifetime relates to expiry, which is the remaining gap for a checkout-preparation step.

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?

Schema coverage is 100%, so the schema already documents offer_id, resource_id and quantity including the 1-100 range and default. The description only restates the offer_id/resource_id alternative in compressed form, adding no syntax or fallback detail the schema lacks, so the baseline 3 applies.

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?

States a specific verb and resource (prepare a checkout) plus the concrete outcome: review the amount and obtain a single-use confirmation. It explicitly separates itself from pay_and_access ('this tool never pays'), so an agent can distinguish the two without opening either schema.

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?

Gives an explicit precondition ('after an accepted offer'), names the alternative for spending ('use pay_and_access to spend'), and states the parameter routing rule ('offer_id, or resource_id ... for the list price'). Both when-to-use and when-not-to-use are covered.

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

All AZPay Monetize — Sepolia Sandbox 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.

Resources

Need Help?