Loading ToolBench

Reading the current corpus…

dsh-mcp-mgr MCP server · F · ToolBench

dsh-mcp-mgr

Workspace-level MCP manager for DeepSeek Harness: discovers .dsh/dshmm/mcp.json per workspace and dynamically registers mcp-client instances

2026-07-28+STDIO1 tools

37/100

Definition Quality37

Protocol Readiness50

Supportability28

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 'ping' with minimal definition. Tool has a basic description (34 chars) and a simple input schema with one string parameter. However, the description is extremely terse and lacks context about when/why to use the tool. No output schema documented. No error handling guidance. The tool appears to be a test/connectivity probe rather than a production-grade agent tool. Tool definition is visible in e2e/mcp-test-server.mjs but this is a test server, not the main MCP server implementation.

Tools (1)

pingread onlysource verified37/100

Test MCP server connectivity with a message echo

Issues (4)

HIGHtool-description ↗

Tool description is too terse (34 chars). Lacks context on when to use, what it returns, and prerequisites. LLMs cannot determine selection criteria.

ping

HIGHtool ↗

No output schema documented. LLMs cannot plan downstream operations or extract return values without knowing the response structure.

ping

MEDIUMrecovery-guide ↗

No error handling guidance. Tool provides no recovery hints if the call fails or times out.

ping

HIGHtool ↗

Tool is a test/connectivity probe (e2e/mcp-test-server.mjs), not a production agent tool. Single-purpose echo utility does not follow agentic tool patterns.

ping

Recommendations

Expand tool description to 50-200 chars: explain that ping tests MCP server connectivity by echoing a message back, useful for health checks and latency measurement.
Document the output schema explicitly: e.g., {"type": "object", "properties": {"echo": {"type": "string", "description": "The echoed message"}, "timestamp": {"type": "string"}}}
Add error handling guidance: 'If the server does not respond within 5 seconds, the connection may be unstable. Retry or check server logs.'
If this is a test server only, clarify in the repo README that it is not intended for production use and serves only e2e validation.
Consider adding production-grade tools beyond connectivity testing (e.g., MCP server lifecycle management, configuration validation, resource discovery).

Score history

Overall score trend

First recorded score · v2 rubric

37/100

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