AI Cloud Studio — Turnkey Multi-Agent SaaS & Digital Bundle Hub

verify_payment_and_unlock

Verifies a Base USDC/USDT or Tonkeeper TON/USDT-TON payment (by tx_hash, wallet address, or order reference) and returns the full unredacted Pro deliverables and 6-file download pack.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tx_hash": "<tx_hash>"
    },
    "name": "verify_payment_and_unlock"
  }
}

Input Schema

Name	Required	Description
`domain`	No	Target domain or query input to unlock
`tx_hash`	Yes	0x... transaction hash, 0x... sender wallet, or TON event/order reference
`plan_price`	No	Paid amount in USD (e.g. 1, 5, 15, 19, or 79)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / plan_price / description

Previous value: -"Paid amount in USD (e.g. 1, 5, 15, 39, or 550)"New value: +"Paid amount in USD (e.g. 1, 5, 15, 19, or 79)"

AddedOct 19, 2026

TDQS

B3.4/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 and does disclose the supported chains (Base USDC/USDT, Tonkeeper TON/USDT-TON) and that output is 'full unredacted' deliverables. However, it omits failure modes (what happens on an unverified/unmatched payment), idempotency, and any auth/permission requirements for a verification-gated unlock.

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?

A single dense sentence with no wasted words, front-loading the verification action before the payoff. It is information-packed rather than bloated, though the parenthetical and trailing clause make it slightly heavy.

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

Completeness3/5

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

Without an output schema, the description usefully sketches the return ('full unredacted Pro deliverables and 6-file download pack') and supported payment rails. But for a security-sensitive verification/unlock operation with no annotations, it should say more about failure behavior and preconditions.

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% and the schema already explains that tx_hash accepts a hash, sender wallet, or TON order reference. The description mirrors this rather than adding new meaning, so the baseline 3 is appropriate; it says nothing about how domain and plan_price affect verification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (verifies) and resource (payment) plus its outcome (unlocks Pro deliverables and a 6-file download pack), with supported chains named. It is clearly distinguishable from siblings like audit_domain and submit_buyer_offer, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent must infer it is called after a payment to unlock content. It names input forms (tx_hash, wallet address, order reference) but gives no when-to-use/ when-not criteria or pointers to alternatives for related steps (e.g., get_package_manifest).

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

All AI Cloud Studio — Turnkey Multi-Agent SaaS & Digital Bundle Hub 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?