Skip to main content
Glama
Sign In

TRON USDT Risk Checker

by io.github.chico10117
OverviewDiscussionsAdmin

Check TRON USDT blacklist

check_tron_usdt_blacklist
Read-onlyIdempotent

Free. Reads the USDT TRC20 contract live and reports whether Tether has blacklisted (frozen) a TRON address. Point-in-time result. Limited per caller per UTC day; failed reads still count toward the limit.

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": {
      "address": "<address>"
    },
    "name": "check_tron_usdt_blacklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesPublic TRON address (base58 T-address, e.g. TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses cost ('Free'), the data source (live read of the USDT TRC20 contract), result freshness ('Point-in-time'), and a quota model ('Limited per caller per UTC day; failed reads still count toward the limit'). The rate-limit detail in particular is exactly the kind of operational context annotations cannot express.

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?

Four short sentences, front-loaded with cost and core behavior, then freshness, then the quota. Every clause carries information an agent would otherwise have to discover by trial; there is no filler or repetition of the name.

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 one-parameter, read-only lookup this is nearly complete: safety profile is covered by annotations, cost and quota are explicit, and the outcome is described in prose. The remaining gap is that no output schema exists and the description does not sketch the response shape (e.g. whether a blacklist flag, an address echo, or a free-form status is returned).

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?

There is a single parameter and schema description coverage is 100%, with the schema itself giving the base58 T-address format and an example. The description adds no further meaning about the address argument (such as whether non-contract or non-existent addresses are accepted), so the baseline 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: it reads the USDT TRC20 contract live and reports whether Tether has blacklisted/frozen a given TRON address. That is unambiguous, but it never distinguishes itself from the siblings screen_tron_address or tron_usdt_aml_report, so an agent cannot tell from the description alone which of the three to pick.

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: an agent infers it should call this when it needs the raw blacklist/freeze status for a single address. The phrase 'Point-in-time result' hints that a fresh call is needed for current state, but there is no explicit when-to-use, when-not-to-use, or routing to the sibling screening/report tools.

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

All TRON USDT Risk Checker 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