Loading ToolBench
Model Context Protocol server for Regen Network blockchain, providing tools for querying ecological credits, baskets, bank balances, and advanced analytics
The server has 31 tools with generally adequate parameter schemas and descriptions, but several critical issues limit quality. Most tools are read-only queries against Regen Network blockchain. Naming is action-verb-based and clear (list_, get_, analyze_). Parameter descriptions are present for most inputs. However, output schemas are not documented in the source code, the responses are inferred but not formally declared. Error handling guidance is absent. Several tools have generic or placeholder descriptions (e.g., cache tools). Three analytics tools (analyze_portfolio_impact, analyze_market_trends, compare_credit_methodologies) have expansive descriptions that include return value hints, but these are narrative rather than formal schemas. The majority of tools (bank, basket, credit, distribution) have minimal but functional documentation. This server is typical of community blockchain tooling, functional but not production-polished.
Analyze market trends across credit types with historical data analysis. Performs comprehensive market trend analysis including price movements, volume patterns, market sentiment, and forward-looking projections.
Analyze the ecological impact of a portfolio with advanced metrics. Provides sophisticated analytical assessment of portfolio ecological impact, including cross-credit impact scoring, diversification analysis, and optimization recommendations.
Clear all cached data.
Compare different credit class methodologies for impact efficiency analysis. Provides detailed comparative analysis of credit class methodologies, including impact efficiency scoring, market performance evaluation, and investment recommendations.
Get detailed account information.
Get all token balances for address.
Get balance of specific token for address.
Output schemas not documented. Tool descriptions include narrative return value hints (e.g., 'Returns: Dictionary containing...') but no formal JSON Schema output definitions. LLMs cannot parse what fields to expect from responses.
Cache management tools (clear_cache_tool, get_cache_stats_tool, invalidate_cache_key_tool) have generic descriptions that do not explain their purpose in the context of the blockchain client. When would an agent or user call clear_cache? What does cache_stats reveal?
No error handling or recovery guidance in any tool description. Tools call external Regen Network APIs but do not document what happens on network failures, invalid addresses, or rate limits. LLMs have no guidance on retry strategies.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 45 | - | v1 |
Retrieve detailed information about a specific basket.
Get balance of a specific credit batch in a basket.
Retrieve current fee required to create a new basket.
Get comprehensive cache performance statistics.
Get spendable (not locked/staked) balances for address.
Get total supply of specific denomination.
Get total supply of all coin denominations.
Invalidate a specific cache key.
List all accounts on Regen Network.
List all credit batches held in a specific basket.
List all active ecocredit baskets on Regen Ledger.
List all issued credit batches on Regen Network. Credit batches represent specific issuances of credits from projects. Each batch has a unique denomination, vintage period, and operational status (open/closed for additional issuance).
List all credit classes (methodologies) on Regen Network. Credit classes define specific methodologies for measuring and verifying ecological benefits within a credit type (e.g., C01, C02 for different carbon methodologies).
List all credit types enabled via governance on Regen Network. Credit types represent the fundamental categories of ecological benefits that can be measured and tokenized (e.g., Carbon, Biodiversity).
List all registered projects on Regen Network. Projects represent specific ecological initiatives that generate credits under approved methodologies. Each project is linked to a credit class and has geographic and temporal boundaries.
Parameter constraints are incomplete. Many numeric pagination parameters (limit, offset, page) lack min/max bounds in descriptions. LLMs can pass unbounded values (e.g., limit=999999) that may break the API or timeout.
Regen Network address format not validated in parameter descriptions. The tool instructions say '(must start with 'regen1')' but this is enforcement guidance, not a regex pattern. Descriptions should state the exact format constraint clearly.
Validator address and delegator address parameters lack format documentation. Are these bech32-encoded Cosmos addresses? If different formats are accepted (display name vs address), this must be explicit.