Loading ToolBench
MCP server for MySSL website SSL/TLS certificate analysis and scanning
Two tools with minimal descriptions and incomplete parameter documentation. fast_analyze lacks context on prerequisites (partnerId/secretKey setup), expected output format, and when to use it. save_config is a setup tool but lacks guidance on consequences. Neither tool documents output schemas. Parameter descriptions are present but generic. No error handling guidance. No mention of API timeouts, rate limits, or failure modes. Schemas are structurally valid but lack constraints (enums, patterns, ranges). This server reads as a thin wrapper around an external API without agent-friendly abstractions.
A tool that scans website by domain (fast analyze).
Save the partnerId and secretKey to the config.
Missing output schema documentation. fast_analyze returns raw API response (decoded UTF-8 text) with no documented structure. LLMs cannot plan downstream actions or extract fields without knowing what to expect.
Incomplete tool descriptions. fast_analyze (47 chars) lacks WHEN to use it, WHAT it returns, and prerequisites. save_config (54 chars) does not explain consequences or when to call it first. Descriptions should be 50-200 chars with clear intent.
Credentials exposed in tool parameters. save_config accepts partnerId and secretKey as parameters. These should be injected server-side via environment variables or config files, never exposed as tool inputs. Agent traces log all parameters.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
No error handling guidance. Code raises ValueError for missing credentials but provides no recovery path. LLM receives raw exception, should return structured error with actionable next steps (e.g., 'Call save_config first with your partnerId and secretKey').
Missing parameter constraints. domain parameter accepts any string with no validation, format hint, or example. Should document expected format (e.g., 'FQDN like example.com, no protocol or path') and validate input.