Loading ToolBench

Reading the current corpus…

arsenal MCP server · F · ToolBench

arsenal

Portable workflow skills and optional continuous Arsenal routing for OMP and Pi. A plugin system for agent-driven development with specialist skills for coding, proposals, shipping, and project management.

2026-07-28+STDIO1 tools

35/100

Definition Quality25

Protocol Readiness50

Supportability43

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 'arsenal-mode' has a basic description (79 chars) but critically lacks a proper input schema. The schema shown is inferred/incomplete: only 'mode' parameter with type 'string' and description, but no enum constraint despite the description listing exactly three valid values ('on', 'off', 'status'). No output schema documented. Tool is a WRITE operation but lacks error handling guidance, recovery paths, or confirmation pattern.

Tools (1)

arsenal-modewritesource verified25/100

Toggle continuous Arsenal routing without restricting Pi. Enables Arsenal mode to act as workflow router for specialist skills.

Issues (5)

CRITICALconstrained-input ↗

Input schema missing enum constraint. Parameter 'mode' accepts only 'on', 'off', 'status' but is defined as free-form string. LLM will hallucinate invalid values.

arsenal-mode

CRITICALtool ↗

No output schema documented. LLM cannot predict what 'arsenal-mode' returns or plan downstream actions.

arsenal-mode

HIGHconfirmation-request ↗

Destructive/write operation lacks confirmation pattern or dry-run support. Toggling 'arsenal-mode' on/off affects routing behavior but has no guard against accidental invocation.

arsenal-mode

HIGHrecovery-guide ↗

No error handling guidance. Tool description does not explain what happens on invalid mode, what errors are retryable, or how to recover.

arsenal-mode

MEDIUMtool ↗

Tool name 'arsenal-mode' is vague. Does not start with action verb. 'toggle-arsenal-mode' or 'set-arsenal-mode' would clarify intent.

Recommendations

Add enum constraint to 'mode' parameter: {"type": "string", "enum": ["on", "off", "status"], "description": "Mode selection: 'on' enables Arsenal routing, 'off' disables it, 'status' returns current state."}
Document output schema: e.g. {"type": "object", "properties": {"mode": {"type": "string"}, "previous_mode": {"type": "string"}, "timestamp": {"type": "string"}}}
Add error handling: 'Returns error if mode is invalid. Retryable: no. User-fixable: yes, ensure mode is one of: on, off, status.'
Rename tool to 'set_arsenal_mode' or 'toggle_arsenal_mode' to clarify action.
Add confirmation pattern for 'on' mode: 'This enables continuous Arsenal routing. Confirm before proceeding.' to prevent accidental activation.

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