These details were reported by Claude Cowork.
Description
get_personal_info returns the user's height as "1.7 cm" for an Oura profile that lists height as 173 cm. The Oura API returns height as a float in metres, so the underlying value is 1.73. The MCP wrapper appears to be printing that value as-is and labelling it cm — both the unit and the truncation are wrong.
Steps to reproduce
Configure the server against an Oura account whose profile height is 173 cm.
Call get_personal_info.
Observe the rendered output:
Height: 1.7 cm
Expected
Either Height: 1.73 m or Height: 173 cm.
Suggested fix
Whichever formatter handles personal_info: if labelling as cm, multiply the API value by 100; if labelling as m, drop the truncation. The neighbouring weight field renders correctly (93.1 kg), so it looks isolated to the height path.
Environment
Package: oura-ring-mcp
Tool: get_personal_info
Date observed: 2026-04-25
Other endpoints (sleep, readiness, activity, ring info) all looked correct.
These details were reported by Claude Cowork.
Description
get_personal_info returns the user's height as "1.7 cm" for an Oura profile that lists height as 173 cm. The Oura API returns height as a float in metres, so the underlying value is 1.73. The MCP wrapper appears to be printing that value as-is and labelling it cm — both the unit and the truncation are wrong.
Steps to reproduce
Configure the server against an Oura account whose profile height is 173 cm.
Call get_personal_info.
Observe the rendered output:
Height: 1.7 cm
Expected
Either Height: 1.73 m or Height: 173 cm.
Suggested fix
Whichever formatter handles personal_info: if labelling as cm, multiply the API value by 100; if labelling as m, drop the truncation. The neighbouring weight field renders correctly (93.1 kg), so it looks isolated to the height path.
Environment
Package: oura-ring-mcp
Tool: get_personal_info
Date observed: 2026-04-25
Other endpoints (sleep, readiness, activity, ring info) all looked correct.