Loading ToolBench

Reading the current corpus…

cuevote MCP server · F · ToolBench

← Browse

cuevote

github.com/loewenmaehne/cuevote

MCP server for CueVote — ops/admin tooling (Phase 1) and AI-DJ control (Phase 2).

2026-07-28+STDIO1 tools

35/100

Definition Quality30

Protocol Readiness50

Supportability32

Spec posture

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

Static source inference · medium confidence

Current-spec patterns detected

Summary

Single tool with minimal definition. cuevote_diagnostics has a description (READ_ONLY status check) but no visible input schema in the source code provided. The tool registration appears in cuevote-mcp/src/index.ts but the actual schema definition is not shown in the provided source excerpt. Tool name lacks a clear action verb (no 'get_', 'list_', etc.) and the description is minimal (~60 chars). No parameter documentation visible. No output schema documented. This server appears to be in early Phase 1 with very limited functionality.

Tools (1)

cuevote_diagnosticsread onlysource verified30/100

Report which CueVote MCP capabilities are configured (DB read access, live-ops admin API, DJ WebSocket bridge). Returns no secrets.

Issues (4)

CRITICALtool ↗

No input schema visible for cuevote_diagnostics. Per HARD SCORING RULE, schema score must be 0.

cuevote_diagnostics

HIGHtool ↗

Tool name 'cuevote_diagnostics' does not start with a clear action verb. Should be 'get_cuevote_diagnostics' or 'describe_cuevote_capabilities'.

cuevote_diagnostics

HIGHtool ↗

No documented output schema. LLMs cannot infer what fields the response contains or plan downstream operations.

cuevote_diagnostics

MEDIUMtool-description ↗

Description is minimal (~60 chars) and does not include WHEN to use the tool, WHAT the expected response structure is, or any prerequisites.

cuevote_diagnostics

Recommendations

Rename 'cuevote_diagnostics' to 'get_cuevote_capabilities' or 'describe_cuevote_status' to follow verb_noun convention.
Add explicit JSON Schema input definition (even if empty object) with 'type: "object", properties: {}, required: []'.
Document the response schema with field names, types, and descriptions. Example: '{"database_read_access": boolean, "liveops_admin_api": boolean, "dj_websocket_bridge": boolean}'.
Expand description to 100-200 characters explaining: 'Returns the current configuration state of CueVote MCP capabilities. Call this first to discover available features before attempting feature-specific operations.'
Add a 'risk' field to the tool definition if not already present, explicitly marking it as READ_ONLY.

Score history

Overall score trend

First recorded score · v2 rubric

35/100

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