AZPay Monetize — Sepolia Sandbox

Get checkout status

get_checkout_status

Read-only

Use this to read whether a checkout is pending, paid, consumed, expired, or cancelled. Use get_receipt to deliver content, and cancel_checkout to invalidate an unused confirmation. Input: confirmation or offer_id. Returns the state, amount, units remaining, and expiry. It does not pay or cancel.

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": "get_checkout_status"
  }
}

Input Schema

Name	Required	Description	Default
`offer_id`	No	Accepted offer id. Pass this or confirmation.
`confirmation`	No	Single-use confirmation from prepare_checkout. Pass this or offer_id.

Output Schema

Name	Required	Description	Default
`note`	Yes
`state`	Yes
`amount`	Yes
`network`	Yes
`testnet`	Yes
`offer_id`	Yes
`expires_at`	Yes
`amount_atomic`	Yes
`schema_version`	Yes
`units_remaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026

removedInput schema / properties / confirmacao

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

changedInput schema / properties / confirmation / description

Previous value: -"Single-use confirmation from prepare_checkout."New value: +"Single-use confirmation from prepare_checkout. Pass this or offer_id."

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. Pass this or confirmation."

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this is a read-only, non-destructive, closed-world operation. The description reinforces that by enumerating status values and stating that it does not pay or cancel, though its summary of return fields overlaps with the existing output schema.

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 short, front-loaded with the core purpose, and each sentence contributes either usage guidance, input clarification, or behavioral boundaries. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a read-only tool with full schema coverage, an output schema, and clear annotations, the description covers everything an agent needs: purpose, alternatives, accepted inputs, and the fact that it does not mutate state.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description only says to pass confirmation or offer_id, which adds no meaningful semantics beyond the schema.

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 specific verb and resource: reading checkout status. It enumerates the possible states (pending, paid, consumed, expired, cancelled) and explicitly distinguishes this read operation from get_receipt and cancel_checkout.

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?

It gives explicit when-to-use guidance, names the alternatives get_receipt and cancel_checkout with their distinct purposes, and states that this tool does not pay or cancel. That leaves little ambiguity about which sibling to select.

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?