Skip to main content
Glama

agtmart sandbox store and agent survey

Confirm a simulated stablecoin payment

confirm_crypto_payment

Confirm a USDC/USDT sandbox payment_request with a FAKE transaction hash (EVM: 0x + 64 hex; Tron: 64 hex; Solana: base58 signature). Hashes ending in 'dead' simulate a reverted tx, 'beef' an underpayment. Requests expire after 15 minutes.

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": {
      "payment_id": "<payment_id>",
      "tx_hash": "<tx_hash>"
    },
    "name": "confirm_crypto_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashYes
payment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, non-destructive, closed-world write. The description adds meaningful behavior beyond that: the environment is a simulator, hash formats differ per chain, suffixes 'dead'/'beef' force reverted/underpayment outcomes, and requests lapse after 15 minutes. It does not say what state changes on success or how repeat calls behave, which would be needed for a 5.

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 dense sentences with no filler: what it does first, then per-chain hash formats, then the simulation triggers and expiry. Every clause carries information an agent needs to invoke it correctly.

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?

For a two-parameter mutation tool with no output schema, the description covers environment, input formats, simulation triggers, and expiry. The remaining gap is the success/return behavior — what confirming actually produces — which the description never states.

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 coverage is 0%, so the description must carry parameter meaning — and it largely does for tx_hash, specifying exact formats for EVM (0x + 64 hex), Tron (64 hex), and Solana (base58), plus magic suffixes that alter outcomes. payment_id is only implied to reference an existing sandbox payment_request; its format is left unstated.

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 names a specific verb ('Confirm') and resource ('a USDC/USDT sandbox payment_request'), and explicitly scopes it to simulated/sandbox payments with a fake hash. No sibling tool in the catalog touches payment confirmation, so an agent can identify this unambiguously.

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 strong operational context for when the call is valid: the target must be a sandbox payment_request, hashes must be fake and formatted per chain, and requests expire after 15 minutes. It does not spell out an explicit when-not or name an alternative path, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources