Loading ToolBench

Reading the current corpus…

energyevals MCP server · F · ToolBench

← Browse

energyevals

github.com/DavidAkinpelu/energyevals

MCP server for energy market analysis, battery optimization, and regulatory docket search tools

<=2025-11-256 tools

48/100

Definition Quality64

Protocol Readiness32

Supportability31

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

EnergyEvals provides 6 tools with explicit schemas and descriptions, but quality is inconsistent. Tool names follow verb_noun convention (battery_revenue_optimization, search_dc_dockets, etc.), which is good. However, descriptions vary widely in clarity and actionability. The battery tool has a detailed, domain-specific description; docket search tools are terse. Parameter descriptions exist but many lack format constraints, ranges, or examples. No output schemas are documented, LLMs cannot predict what fields to expect. Error handling is absent from visible code. No tool annotations (readOnlyHint, destructiveHint) despite several tools being read-only. The codebase shows a ToolResult class with success/error/data fields, but this is not reflected in tool definitions exposed to LLMs.

Tools (6)

battery_revenue_optimizationread onlysource verified77/100

Produces optimal potential net revenues for battery storage projects using energy arbitrage only (perfect price foresight, no price-uncertainty penalty). Reads a CSV of energy prices and returns summary metrics, time-series rows, and a saved CSV path.

get_maryland_official_filingsread onlysource verified62/100

Search Maryland PSC 'Official Filings' by date range.

get_maryland_psc_itemread onlysource verified62/100

Fetch a Maryland PSC item (case/rulemaking/public conference) by number. For rulemaking, number should have a prefix RM and PC for public conference. No prefix needed for case.

search_dc_docketsread onlysource verified60/100

Search DC PSC filings by date range from the eDocket system.

search_ferc_docketsread onlysource verified65/100

Search the FERC eLibrary using the AdvancedSearch API for filings and dockets. Returns source, keyword, date range, number of results, detailed results, and a saved CSV path.

search_new_york_docketsread onlyauthsource verified58/100

Search New York DPS cases or documents between dates.

Issues (5)

CRITICALtool ↗

No output schemas documented. LLMs cannot predict response structure, forcing them to guess what fields are available for downstream tool chaining.

battery_revenue_optimizationsearch_dc_docketssearch_ferc_docketsget_maryland_psc_itemget_maryland_official_filingssearch_new_york_dockets

HIGHtool-description ↗

Docket search tools lack actionable descriptions. 'Search DC PSC filings by date range' does not explain when to use this vs FERC/Maryland/NY tools, what data is returned, or how results enable downstream actions.

search_dc_docketssearch_ferc_docketssearch_new_york_dockets

HIGHconstrained-input ↗

Parameter descriptions lack format constraints and ranges. E.g., 'start_date' says 'MM/DD/YYYY format' but no validation guidance. 'records_to_show' has no min/max bounds, LLM could pass 10000.

search_dc_docketssearch_ferc_docketssearch_new_york_dockets

Recommendations

Document output schemas for all tools. E.g., battery_revenue_optimization should declare: {success: bool, summary_metrics: {net_revenue: float, cycles: int, ...}, time_series: [{timestamp, soc, revenue, ...}], csv_path: string}. This enables LLMs to chain results.
Expand docket search descriptions to 100-150 chars explaining: (1) what jurisdiction/source it queries, (2) what fields are returned, (3) when to use it vs other docket tools. E.g., 'Search DC PSC filings (utility regulation cases) by date, keyword, or docket number. Returns filing metadata, case type, and document links. Use for DC-specific regulatory filings.'
Add min/max bounds to numeric parameters. E.g., records_to_show: 1-500 (default 50), timeout: 5-120 seconds (default 30). Add regex or enum constraints to date parameters.
Add readOnlyHint: true to all 6 tool definitions in the MCP schema. This signals to agents that these tools are safe to retry and have no side effects.
Implement error recovery guidance in tool implementations. When a docket search times out or returns 0 results, return: {success: false, error: 'Search timed out after 30s. Try narrowing date range or removing keywords.', recovery_suggestion: 'Retry with shorter date range or fewer keywords.'}. Expose this in tool descriptions.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

48/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	48	<=2025-11-25	v2