Loading ToolBench

Reading the current corpus…

jpdcl MCP server · C · ToolBench

← Browse

jpdcl

github.com/ashfaqmehmood/jpdcl

Unofficial Jammu Power Distribution Corporation Limited (JPDCL) smart-meter MCP, CLI, REST API, and TypeScript client

2025-06-18+STDIO27 tools

61/100

Definition Quality76

Protocol Readiness47

Supportability45

Spec posture

Inferred effective spec 2025-06-18+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration, stateful session

Deprecated protocol patterns detected

Summary

Server has 27 tools with mostly complete schemas and descriptions. Naming follows verb_noun convention (jpdcl_*). Most tools have 50-150 char descriptions and proper JSON Schema with types. However, several tools lack parameter descriptions (e.g., jpdcl_smart_report 'end' param), some descriptions are generic ('Get X'), and output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages visible. Tool composition is reasonable but some tools overlap (jpdcl_snapshot vs jpdcl_account_digest). No evidence of input validation or constraint enforcement beyond enums.

Tools (27)

jpdcl_account_digestread onlyauthsource verified73/100

Get a digest of account information including bills, payments, and consumption

jpdcl_account_inforead onlyauthsource verified77/100

Get detailed customer account information

jpdcl_auth_loginwritesource verified80/100

Authenticate with JPDCL using login ID and password

jpdcl_billsread onlyauthsource verified80/100

Get bill history for an account

jpdcl_catalogread onlysource verified83/100

List available JPDCL endpoints and their metadata

jpdcl_consumptionread onlyauthsource verified80/100

Get electricity consumption data for an account

jpdcl_energy_ledgerread onlyauthsource verified78/100

Get daily energy ledger with meter readings and consumption data

Issues (5)

HIGHtool ↗

Output schemas not documented. Tools return data but LLMs cannot plan downstream calls without knowing response structure. Affects all 27 tools.

jpdcl_snapshotjpdcl_account_infojpdcl_billsjpdcl_consumptionjpdcl_smart_dashboard

HIGHtool-description ↗

jpdcl_smart_report has undescribed parameter 'end' (type number). LLM cannot infer its purpose or valid range.

jpdcl_smart_report

MEDIUMtool-description ↗

Generic descriptions like 'Get X' or 'Get Y data' lack context for when to use the tool vs similar ones. jpdcl_snapshot vs jpdcl_account_digest vs jpdcl_account_info are unclear.

jpdcl_snapshotjpdcl_account_digestjpdcl_account_info

HIGHrecovery-guide ↗

No error handling guidance. Tools return errors but do not tell LLM what to do next (retry, ask user, abort). No recovery patterns visible.

all

Recommendations

Document output schemas for all tools. Include field names, types, and what IDs/references are returned for chaining. Example: 'Returns {accountId, bills: [{billId, amount, dueDate}], totalBills}'.
Add parameter descriptions to jpdcl_smart_report 'end' param and any others missing them. State the expected type, range, and purpose.
Distinguish jpdcl_snapshot, jpdcl_account_digest, and jpdcl_account_info in descriptions. State which is for AI analysis, which for billing, which for full details.
Implement error recovery guidance. Return structured errors like '{error: "account_not_found", message: "Account ABC not found", suggestion: "Try jpdcl_catalog to list available accounts"}'.
Move loginId/password from tool parameters to environment variables or secure config. Implement OAuth or token-based auth instead of exposing credentials in tool calls.

Spec posture evidence

Inferred effective spec: 2025-06-18+.

Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained

Score history

Overall score trend

First recorded score · v2 rubric

61/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	C	61	2025-06-18+	v2