MCP server for analyzing biomarker data and suggesting monitoring priorities for health metrics
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. analyze_biomarkers has a nested object schema for biomarkers array with reasonable structure (name, value, category, range), but lacks output schema documentation. suggest_monitoring_priorities has similar input structure but omits the 'category' field in items compared to analyze_biomarkers, creating inconsistency. Both descriptions are adequate (50-60 chars) but generic. No error handling guidance, no parameter constraints (enums, ranges), and no documentation of what the tools return. Tool names follow verb_noun pattern (analyze_, suggest_) which is good, but descriptions lack WHEN/WHY context for LLM selection.
Identify concerning values and potential health risks from biomarker data
Recommend which biomarkers need closer attention based on current values
Output schemas not documented. LLMs cannot plan downstream calls or extract results without knowing what fields to expect.
Parameter descriptions lack constraints. 'value' is a number with no min/max bounds; 'category' has no enum or valid values listed. LLMs will pass invalid data.
Inconsistent input schemas between tools. analyze_biomarkers includes 'category' in biomarker items; suggest_monitoring_priorities omits it. LLMs will struggle with field mapping.
Tool descriptions are generic and lack WHEN/WHY context. 'Identify concerning values' does not explain when to call this vs suggest_monitoring_priorities or how results differ.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
No error handling guidance. If biomarker data is invalid or missing, tools provide no recovery hints. LLMs cannot self-correct.