Skip to main content
Glama
Sign In

TronProof

by online.tronproof
OverviewDiscussionsAdmin

verify_usdt_payment

Confirms whether a Tron address received a specific amount of genuine USDT within a time window. Ignores fake tokens that copy the USDT name. Use before releasing goods, crediting an account or marking an invoice paid. Costs $0.005 per call in USDC on Base (x402).

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": {
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "verify_usdt_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTron address that should have received the payment
fromNoOptional sender address the payment must come from
txidNoOptional transaction id the payment must match
matchNo"exact" (default) or "at_least"
amountYesExpected USDT amount, for example 25 or 25.50
minutesNoHow far back to look, 1 to 10080. Default 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 does disclose two important behaviors: fake tokens that copy the USDT name are ignored, and each call costs $0.005 in USDC on Base via x402. It does not say what the response looks like, what happens when several transfers match, or how failures are reported.

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 short sentences, front-loaded with the core behavior, then usage, then cost. Every sentence carries information and there is no filler.

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 no annotations and no output schema, the description does well on purpose, trigger conditions, token authenticity, and pricing. It leaves a gap: the shape of the result — a boolean or matched-transfer detail — is left implicit, which matters for a verification tool.

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 all six parameters are already documented in the schema. The description only loosely echoes the amount and time-window semantics without adding meaning such as rounding, how from/txid narrow matching, or how at_least behaves. The baseline of 3 applies.

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?

The description gives a specific verb and resource: confirms whether a Tron address received a given amount of genuine USDT within a time window. That is functionally distinct from listing transfers or checking address risk, though no sibling is named explicitly.

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 clearly says when to use it: before releasing goods, crediting an account, or marking an invoice paid. It does not state when not to use it or name an alternative tool, so it falls 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.

All TronProof toolsInspect
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