A web-based fasting tracker with MCP (Model Context Protocol) server integration for agent-controlled fasting management, experiment tracking, and history analytics
Critical gaps across naming, descriptions, and schemas. Tool names lack consistent verb prefixes (e.g., 'preview_fast_end' vs 'get_current_fast'). Only 3 of 17 tools have visible input schemas in source; 14 tools have no documented parameters. Descriptions are present but generic (avg ~50 chars, well below 194-char baseline). No output schemas documented. No error handling guidance. Tool definitions appear inferred from constant array rather than explicit registration with full metadata.
Adjust the start time of the currently active fasting session
Cancel the currently active fasting experiment
Compare fasting metrics between two time periods
Create a new fasting tracking experiment with specified parameters
Create a custom historical data visualization view
Retrieve details of the currently active fasting experiment
14 of 17 tools have no visible input schemas in source code. Only 3 tools (get_fasting_summary, create_fasting_experiment, cancel_active_experiment, start_fast, stop_active_fast, adjust_active_fast_start) show parameter definitions. Tool definitions appear inferred from a constant array rather than explicit registration.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure. Missing pagination info for list_recent_fasts and get_agent_activity.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Retrieve the activity log of agent-initiated actions
Retrieve the currently active fasting session
Get a summary of fasting statistics over a specified period
Highlight specific fasting records in the history view
List recent completed fasting sessions
Preview the outcome of ending the current fast
Preview the consequences of a fasting-related decision before applying it
Change the visual display mode of the tracker interface
Configure the visual layout of the tracker workspace
Start a new fasting session with a specified target duration
End the currently active fasting session
Descriptions are generic and under 50 characters for most tools (e.g., 'Retrieve the currently active fasting session'). Lack context on WHEN to use vs similar tools, prerequisites, or what data is returned. Baseline is 194 chars.
Ambiguous tool names: 'preview_fast_end' and 'preview_fasting_decision' both preview outcomes but differ in scope. 'compare_fasting_periods' lacks clarity on what metrics are compared. Names do not clearly distinguish from similar tools.
No error handling guidance. Tools like start_fast, stop_active_fast, and create_fasting_experiment are destructive/irreversible but lack confirmation patterns or recovery instructions. No indication of retryable vs fatal errors.