Loading ToolBench

Reading the current corpus…

BSC-MCP MCP server · F · ToolBench

← Browse

BSC-MCP

github.com/ZiaoLiu-1/BSC-MCP

Model Context Protocol server for BSC chain interaction

2026-07-28+STDIO23 tools

36/100

Definition Quality39

Protocol Readiness50

Supportability23

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

This server has significant definition quality gaps. Tool names are inconsistent (mix of snake_case and dot notation; 'get_top_traders' vs 'wallet.create'). Descriptions are present but generic and lack actionable context (e.g., 'Get top traders for a token on BSC' does not explain when to use this vs. 'get_top_traders_gmgn'). Parameter descriptions are minimal, many lack format/range guidance. Output schemas are not documented. Error handling is absent, no recovery guidance or categorization. Security concerns: wallet operations expose private key handling without documented safeguards. Composition is poor: 23 tools with overlapping functionality (e.g., 6 variants of 'get top traders') without clear differentiation.

Tools (23)

fetch_token_tradesread onlysource verified60/100

Fetch token trades from gmgn.ai API

get_latest_token_transfersread onlyauth50/100

Get latest transfers of a token on Four Meme

get_latest_trades_of_tokenread onlyauth50/100

Get latest trades of a token on Four Meme

get_liquidity_added_eventsread onlyauth50/100

Track liquidity add events for all tokens on Four Meme

get_multiple_top_traders_gmgnread only50/100

Get top traders for multiple tokens in a single call

get_multiple_top_traders_gmgn_tronread only50/100

Get top traders for multiple tokens on Tron in a single call

get_newly_created_tokens_on_four_memeread onlyauth50/100

Get newly created tokens on Four Meme

get_token_trades_gmgnread only50/100

Get token trades from GMGN

Issues (5)

CRITICALtool-description, constrained-input ↗

Five critical tools have empty input schemas ({}): wallet.create, wallet.import, wallet.send, token.transfer, token.approve. These tools are non-functional without parameter documentation.

wallet.createwallet.importwallet.sendtoken.transfertoken.approve

HIGHtool ↗

Inconsistent naming convention: mix of snake_case (get_newly_created_tokens_on_four_meme) and dot notation (wallet.create, token.list). LLMs struggle with inconsistent naming. Standardize to verb_noun format (e.g., create_wallet, send_transaction).

wallet.createwallet.importwallet.listwallet.balancewallet.sendtoken.listtoken.balancetoken.transfertoken.approve

HIGHtool-composition ↗

Six overlapping 'get top traders' tools (get_top_traders_gmgn, get_top_traders_gmgn_tron, get_multiple_top_traders_gmgn, get_multiple_top_traders_gmgn_tron, get_top_traders, fetch_token_trades) with unclear differentiation. LLMs cannot reliably choose between them. Consolidate or add explicit 'when to use' guidance in descriptions.

Recommendations

Add complete input schemas to wallet.create, wallet.import, wallet.send, token.transfer, and token.approve. Specify required fields, types, and constraints (e.g., wallet.send: {address: string, to: string (valid Ethereum address), amount: string (positive decimal), data?: string}).
Standardize all tool names to verb_noun format (e.g., create_wallet, import_wallet, send_transaction, list_tokens, get_token_balance, approve_token_spending). Remove dot notation.
Consolidate overlapping trader tools: merge get_top_traders_gmgn, get_top_traders_gmgn_tron, and variants into a single get_top_traders tool with a 'chain' parameter (bsc|tron) and 'batch' boolean. Add descriptions explaining when to use batch vs. single-token queries.
Document output schemas for all tools. Example for wallet.send: {transactionHash: string, from: string, to: string, amount: string, status: 'pending'|'confirmed'|'failed', blockNumber?: number}. Include chaining IDs (e.g., transactionHash for follow-up queries).
Add security and error handling: (1) Document private key encryption and storage for wallet operations. (2) Add dry-run/confirmation pattern for irreversible operations (wallet.send, token.transfer). (3) Return actionable error messages (e.g., 'Insufficient balance: have 0.5 BNB, need 1.0 BNB' instead of generic errors).

Score history

Overall score trend

First recorded score · v2 rubric

36/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	36	2026-07-28+	v2