Loading ToolBench
MCP server for generating plots, diagrams, and 3D visualizations via Cloudflare Workers
Server has 8 tools with schemas and descriptions, but quality is inconsistent. Tool names are generic (plot, diagram, geometry_3d) without action verbs. Schemas are present but many parameters lack descriptions. The 'health' and 'analysis' tools are stubs. No error handling guidance visible. Output schemas are not documented. This is a typical C-grade community server with significant gaps in LLM-optimization.
Perform analysis operations (placeholder for future implementation)
Generate various types of diagrams (force, circuit, venn, c_memory)
Generate 3D geometric shapes and visualizations
Health check endpoint for the MCP server
Generate a plot from a mathematical expression or multiple expressions
Generate a plot from series data with multiple visualization types
Generate teaching templates for various physics and mathematics topics
Most parameters lack descriptions. E.g., plot tool has 'expr', 'x_min', 'x_max', 'points' with no explanation of format, range, or constraints. LLMs cannot infer parameter meaning from names alone.
Tool names lack action verbs. 'plot', 'diagram', 'geometry_3d' are nouns, not verbs. Should be 'generate_plot', 'create_diagram', 'render_3d_geometry' to signal intent to LLMs.
No output schemas documented. Tools return data but LLMs don't know what fields to expect. E.g., does 'plot' return a URL, JSON, or SVG? This breaks downstream tool chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Generate specialized templates for force analysis and circuit diagrams
'analysis' tool is a stub with empty input schema and 20-char description ('Perform analysis operations (placeholder for future implementation)').
Complex nested schemas (diagram, geometry_3d, plot_series) lack clarity on required vs optional fields and interdependencies. E.g., diagram's 'components' and 'wires' are both optional but may require each other depending on diagram_type.