Loading ToolBench
MCP server for Shape blockchain data - gasback analytics, NFT insights, network monitoring, etc.
The Shape MCP server presents 4 read-only tools focused on blockchain analytics (gasback earnings, creator rankings, earnings simulation, and NFT market stats). Tool naming follows verb_noun convention (all start with 'get' or 'simulate'), which is correct. Descriptions are present for all tools and parameters, ranging 70-170 chars, within baseline (194 char average). However, parameter descriptions lack detail about constraints, format expectations, and usage context. Input schemas are properly typed (string, number) with some defaults provided (hypotheticalTxs=100, avgGasPerTx=150000). Critical gaps: (1) no documented output schemas, LLMs cannot know what fields to expect or plan downstream tool calls; (2) parameter descriptions are minimal and lack constraints or format guidance; (3) no pagination/limit parameters visible despite querying analytics data that could return large result sets; (4) error handling not evident in source snippets, no recovery guidance for failed API calls. Tool composition is single-responsibility (each tool addresses one analytics concern), which is appropriate. The server uses xmcp framework with HTTP transport, supporting tool annotations (readOnlyHint visible in FEATURES), which aligns with current spec.
Get market statistics from Rarible: floor price, volume, and trading activity
Get Shape creator analytics: gasback earnings, balance, withdrawals, tx volume, and registered contracts.
Get Shape top creators by gasback earnings.
Simulate potential Gasback earnings for a creator based on hypothetical number of transactions and average gas used per transaction.
No documented output schemas for any tool. LLMs cannot infer what fields are returned, preventing composition of downstream tools and forcing agents to guess field names.
Parameter descriptions lack constraint information. 'creatorAddress' and 'collection' parameters have no format/validation hints (e.g., 'Ethereum address format: 0x...' or 'contract address (0x...)'); avgGasPerTx provides examples but no clear min/max bounds.
getTopShapeCreators accepts zero parameters. No pagination control (limit, offset, page_size) visible, if the tool returns hundreds of creators, results will exceed context window. Tool description does not specify result limit.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Error handling strategy not documented in tool descriptions. No guidance on what to do if a creator address is invalid, RPC call fails, or Rarible API is unavailable. Agents cannot self-correct.
Parameter descriptions are generic. 'The creator/owner address to analyze gasback data for' lacks clarity on what format is expected, whether it must be on Shape network, or whether alternative address formats are accepted.