Compilation of small app tools with UI to use through MCP
Critical failures across all tools. Descriptions are minimal (10-20 chars) and lack context for LLM selection. Three tools (pizza-map, solar-system, todo-list) have identical, nonsensical parameter schemas (pizzaTopping) that don't match their purpose. get-calculator has zero input parameters despite being a calculation tool. No output schemas documented. No error handling guidance. No parameter descriptions. Naming is weak: 'get-calculator' is vague (get what calculation?), and widget tools lack action verbs.
Get the result of a calculation based on the provided input
Show Pizza Map
Show Solar System
Show Todo List
Empty input schemas: get-calculator has {} with no properties; pizza-map, solar-system, todo-list all have identical pizzaTopping parameter that doesn't match tool purpose.
'Get the result of a calculation' and 'Show Pizza Map' lack context for when/why to call each tool.
No parameter descriptions. pizzaTopping parameter has a description, but get-calculator has no parameters at all. LLMs cannot infer what inputs are needed or how to use them.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 30 | 2026-07-28+ | v2 |
No output schemas documented. Callers cannot know what fields to expect from tool responses, breaking downstream tool chaining and forcing LLMs to guess at response structure.
Weak naming: 'get-calculator' is vague (get what calculation?). Widget tools lack action verbs (pizza-map, solar-system, todo-list should be show_* or render_*). Names do not convey intent.