Loading ToolBench
MCP server for synthesizing vector-based promotional poster and banner layouts with golden ratio optimization and optical kerning
This server has a single tool with a name that violates core conventions. The tool name 'execute_skill_action' uses a generic verb ('execute') rather than a domain-specific action verb. The description is extremely brief (61 characters) and lacks critical context about when/why to use it. The input schema has types and descriptions, which is a minor positive, but parameter descriptions are generic and lack examples or constraints. The output schema is entirely absent, there is no documentation of what the tool returns, which violates a fundamental pattern requirement. The server is STDIO-only, which is a transport hard cap of 50.
Execute promotional poster and banner layout synthesis skill
Tool name uses generic verb 'execute' instead of domain-specific action. Should be 'synthesize_poster_layout' or similar. Generic verbs ('execute', 'process', 'handle', 'run', 'do') prevent LLMs from inferring intent from the name alone.
Tool description is only 61 characters ('Execute promotional poster and banner layout synthesis skill'). Minimum production baseline is ~80-100 chars. Missing: WHAT precisely happens, WHEN to call it, and what happens to state (e.g., 'Creates a new layout job in the GenPark vector synthesis service and returns SVG/PDF URLs for download').
No output schema documented. The tool returns 7 fields (layout_job_id, dimension_format, golden_ratio_layout_score_pct, optical_kerning_applied, vector_poster_svg_url, high_resolution_print_pdf_url) visible only in client.py example, not in the MCP server definition. LLMs cannot plan downstream use without knowing return structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 27 | 2026-07-28+ | v2 |
Parameter descriptions lack specificity and examples. 'The poster/banner dimension format' does not explain valid values. Should include enum or pattern: 'One of: METRO_BUS_SHELTER_POSTER, BANNER_WEB_HERO_1920X1080, etc.' LLMs frequently hallucinate invalid values without explicit constraint documentation.
No error handling or recovery guidance. Tool does not document failure modes, retryability, or what to do if layout synthesis fails. Pattern: error responses must tell the LLM what to do next.
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Must migrate to Streamable HTTP or HTTP+SSE for production use.