AI Agent Skills for TRON

Understand the difference between TronGrid MCP tools and standalone skill packages, and explore the queries each skill covers.

What Are Skills?

Skills are reusable instruction sets that organize workflows such as account analysis and transaction queries. TronGrid’s standalone skill packages are published on ClawHub and must be installed and loaded into the AI client that will use them.

TronGrid MCP exposes callable on-chain tools. Once connected, an AI client can select tools in response to a question. Connecting MCP does not automatically install or load standalone skill packages from ClawHub.

Usage

Ask questions using MCP tools

Configure the TronGrid MCP service using the MCP guide, then ask the client about accounts, transactions, or blocks. Tool selection depends on the client and its configuration.

Use standalone skill packages

Use the table below to open a skill’s detail page, which includes its purpose, example questions, and ClawHub entry. The skill package defines the workflow, while TronGrid MCP provides the tools used by that workflow. Both must be configured.

The following example uses the Account Profiling skill with OpenClaw. The installation command is provided on the skill’s ClawHub page. See the OpenClaw Skills documentation for how skills are loaded.

  1. Install the skill package. In an existing OpenClaw setup, install the Account Profiling skill into the current agent’s workspace:

    openclaw skills install @greason/trongrid-account-profiling
  2. Connect to TronGrid MCP. Add a remote MCP server using the OpenClaw MCP configuration instructions. See the MCP guide for the server URL and request headers. Make sure the agent using the skill can call the required tools, such as getAccount and getAccountResource.

  3. Check the skill and ask a question. Run openclaw skills list --eligible and confirm that Account Profiling appears in the available skills. If it does not, run openclaw skills check to identify missing dependencies; see the Skills CLI documentation. Once the skill is available, start a new session and enter the following request, replacing the placeholder with an actual address:

    Use the trongrid-account-profiling skill to analyze the assets, resources, and recent transactions of <TRON_ADDRESS>.
  4. Check the tool results. Review the client’s tool-call records to confirm that TronGrid MCP tools were called and returned data. If a tool is unavailable or a call fails, check the MCP connection, tool permissions, and error details before continuing.

For other skills, follow their respective ClawHub installation instructions. When using another client, configure skill loading and MCP connections according to that client’s documentation; the OpenClaw installation command above is not a universal command.

Available Skills

SkillExample QuestionsPurpose
Account Profiling"Analyze this wallet"Analysis of account assets, resources, and activity
Block Info"What is the latest block?"Block data, rewards, producer info, and transaction breakdown
Contract Analysis"What information about this contract needs further investigation?"Smart contract information, including ABI, callers, and potential risk indicators
Data Insights"How is the TRON network doing?"Network analytics with activity metrics and trending data
Token List"Top TRON tokens"Token discovery with market metrics and rankings
Token Scanner"Tell me about USDT on TRON"Token supply, holder distribution, and activity data
Transaction Info"Check transaction [hash]"Transaction decoding with resource consumption and event logs
TRX Info"TRX price", "TRX burn rate"TRX economics with supply dynamics and network metrics

Use Cases

Investment Analysis

Contract and transaction inspection

Data Research

Troubleshooting

MCP Server Not Connected

Symptoms: The client cannot find TronGrid MCP tools

Solutions:

  1. Check the server URL and connection settings for your client using the MCP guide
  2. Reconnect to the TronGrid MCP service; restart the client if required
  3. Verify the connection with the curl test in the MCP guide

Invalid API Key

Symptoms: Authentication errors on tool calls

Solutions:

  1. Check that your API key is valid in the TronGrid console
  2. Update the TRON-PRO-API-KEY header in the MCP server configuration
  3. Reconnect to the MCP service to apply the updated configuration

Rate Limit Exceeded

Symptoms: Requests rejected, rate limit error

Solutions:

  1. Ensure requests include a valid API key
  2. Retry rate-limited requests with exponential backoff
  3. Contact TronGrid to request a custom quota if higher throughput is required

Related Resources