tronscan-sr-governance

# SR / Witness (Super Representative) ## Overview | Tool | Function | Use Case | |------|----------|----------| | getWitnessList | Witness/SR list | SRs, partners, candidates by type | | getAccountVotes | Account vote record | Which SRs an address voted for and amounts | | getChainParameters | Chain parameters | Tx fees, energy/bandwidth price, config | | getProposals | Governance proposals | Proposal content, votes, participants | | getWitnessVoteInfo | SR vote metrics | Vote count, ranking history for a witness | | getWitnessGeneralInfo | Network aggregate | Total votes, block stats, witness count | ## Workflow: SR & Voting Queries > User: "Who are the top SRs? What are the chain parameters?" 1. **tronscan-sr-governance** — `getWitnessList` → SR/partner/candidate list; optionally filter by type. 2. **tronscan-sr-governance** — `getWitnessGeneralInfo` → total votes, block stats, witness count. 3. For **chain config** (fees, energy/bandwidth price): `getChainParameters`. > User: "Which SRs did this address vote for?" 1. **tronscan-sr-governance** — `getAccountVotes` with address → vote targets and amounts. > User: "What is the vote/ranking history of SR X?" 1. **tronscan-sr-governance** — `getWitnessVoteInfo` with witness address → vote metrics and history. > User: "Who voted for SR X?" or "List voters of SR X" 1. **tronscan-account-profiler** — `getVoteList` (Account API) with SR address → voter list. ## MCP Server - **Prerequisite**: [TronScan MCP Guide](https://mcpdoc.tronscan.org) ## Tools ### getWitnessList - **API**: `getWitnessList` — Get Super Representative list - **Input**: Supports type filter (SR / partner / candidate) - **Use when**: User asks for "SR list", "super representatives", or "candidates". - **Response**: SR list with vote count, ranking, etc. ### getAccountVotes - **API**: `getAccountVotes` — Get account vote record - **Input**: Account address - **Use when**: User asks "who did this address vote for", "my votes", or "vote destination of an address". - **Response**: SRs voted for and vote amounts. ### getChainParameters - **API**: `getChainParameters` — Get current TRON blockchain configuration parameters - **Use when**: User asks for "chain parameters", "transaction fees", "energy price", "bandwidth price", or "network config". - **Response**: All chain parameters including tx fees, energy/bandwidth price. ### getProposals - **API**: `getProposals` — Get governance proposal list - **Use when**: User asks for "governance proposals", "proposal list", or "voting proposals". - **Response**: Proposal content, vote info, participant details. ### getWitnessVoteInfo - **API**: `getWitnessVoteInfo` — Get vote metrics and history for a specific witness - **Input**: Witness address - **Use when**: User asks for "SR X's votes", "SR ranking change", or "witness historical data". - **Response**: Vote count, ranking change, and other metrics. ### getWitnessGeneralInfo - **API**: `getWitnessGeneralInfo` — Get witness aggregate statistics - **Use when**: User asks for "total votes", "block stats", "witness count", or "network vote overview". - **Response**: Total vote count, block stats, witness count, etc. ## Troubleshooting - **MCP connection failed**: If you see "Connection refused", verify TronScan MCP is connected in Settings > Extensions. - **API rate limit / 429**: TronScan API has call count and frequency limits when no API key is used. If you encounter rate limiting or 429 errors, go to [TronScan Developer API](https://tronscan.org/#/developer/api) to apply for an API key, then add it to your MCP configuration and retry. ### Invalid witness address Ensure the address is a valid TRON base58 format (starts with T). For voter list of an SR, use `getVoteList` (Account API) with the SR address.