usdt-agent-skills-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_usdt_paymentB | Check whether USDT transfers to an address meet a minimum amount on tron, bsc, ethereum, or solana using free public APIs. |
| validate_addressC | Basic format validation for a wallet address on tron, bsc, ethereum, polygon, or solana. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
check_usdt_payment verifies transfer amounts, while validate_address performs format validation—two clearly distinct purposes with no overlap. An agent can easily select the right tool based on the task.
Both tools follow a consistent verb_noun snake_case pattern (check_usdt_payment, validate_address). The naming is predictable and readable.
Two tools is thin for a server that covers USDT payments across multiple chains. While the 'lite' label suggests minimalism, the count feels borderline under-scoped for the domain.
The surface covers payment verification and address validation but lacks operations like fetching transaction details, generating payment requests, or listing supported tokens. These gaps may force agents to work around missing functionality.