personal-health-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALTH_PLANET_CLIENT_ID | Yes | Client ID for Tanita Health Planet API | |
| HEALTH_PLANET_REDIRECT_URI | Yes | Redirect URI for OAuth flow | |
| HEALTH_PLANET_CLIENT_SECRET | Yes | Client secret for Tanita Health Planet API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_body_compositionA | Return the most recent body composition record within the last 30 days. |
| get_body_compositionA | Return body composition data for a date range (max 92 days). |
| get_measurements_rangeA | Return the date range and total count of cached body composition data. |
| get_profileA | Return user profile (birth_date, height_cm, sex) from cache or API. |
| list_available_metricsB | Return the list of available metrics and their descriptions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools are clearly distinct: get_latest_body_composition, get_body_composition, get_measurements_range, get_profile, and list_available_metrics each target different data or metadata. The minor overlap between 'latest' and 'range' variants is manageable due to clear descriptions.
Tool names predominantly follow a get_<resource> pattern, which is consistent and readable. The exception is list_available_metrics, which uses 'list_' instead of 'get_', a minor deviation that does not impede understanding.
Five tools is well within the ideal 3-15 range and appropriately scoped for a personal-health MCP focused on body composition and profile retrieval. No unnecessary tools are present.
The tool set covers read access to body composition data, profile information, and available metrics, but lacks write operations or management of cached data. Since the domain appears to be read-only retrieval from an external source, the core needs are met, though a few potential gaps exist (e.g., no single-metric query).