@tronhooks/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRONHOOKS_API_KEY | No | API key from a local environment/secret manager. Required for account reads (e.g., list_watches, list_events, prepare_delete_watch); capability, validation, and creation-preview tools work without it. Never paste the key into chat, URLs, tracked client configuration, or command-line 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_capabilitiesA | TRON mainnet USDT/TRX confirmed transfer notifications via webhook or Telegram. No balance thresholds, arbitrary tokens, other chains or funds transfer. Return official capability facts and documentation; no account key needed. |
| validate_watch_configB | Validate a TRON USDT/TRX watch draft without DNS lookup, account change or notification. Address shape is checked; the service checks checksum, receiver policy, quota and Telegram binding during confirmed creation. |
| list_watchesA | Read watches scoped to your local mainnet API key. Receiver paths, query strings and secrets are omitted. Does not create, delete or send. |
| list_eventsA | Read retained TRON delivery records for your account. Follow next_cursor unchanged; deleted-watch history is unavailable. This is reconciliation data, not a balance or funds-transfer tool. |
| prepare_create_watchA | Prepare (DO NOT EXECUTE) a TRON USDT/TRX watch creation. Returns a private browser-fragment draft for the owner to review and confirm in the official console. No key or secret in the link. Does not send a notification or create a watch. |
| prepare_delete_watchA | Prepare (DO NOT EXECUTE) deletion of an owned watch after a scoped GET. Owner confirms in the console. Deletion removes notification/attempt history; an in-flight delivery may finish. This tool never calls DELETE. |
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 6 tools
Each tool targets a clearly distinct action+resource: capabilities retrieval, config validation, listing watches, listing events, and prepare-create vs prepare-delete. The descriptions explicitly delimit scope (e.g. 'does not create', 'never calls DELETE'), so misselection is unlikely.
All names follow a consistent snake_case verb-first pattern (get_, validate_, list_, prepare_). The prepare_create_watch / prepare_delete_watch pair is symmetric, reinforcing the pattern.
Six tools is well-scoped for a watch-management server; each tool maps to a distinct step in the lifecycle. Nothing feels redundant or padded.
The surface covers capabilities, validation, listing, event reconciliation, and prepare-create/delete (execution deliberately delegated to the console). Minor gaps exist: no read-single-watch/get-watch, no get-event, and no update-watch operation.