@indaco/garmin-personal-mcp 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indaco/garmin-personal-mcp",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "MCP server for the official Garmin Connect Personal API",
   "homepage": "https://github.com/indaco/garmin-personal-mcp#readme",
   "bugs": "https://github.com/indaco/garmin-personal-mcp/issues",

package/prompts/dashboard-setup.md

@@ -21,9 +21,9 @@ such a tool, ask the questions in chat as numbered lists, with the default first
      HR zones, activity names. For me, all are selected by default; for a shared page, ask about each
      one. The server leaves out of the file what I do not select.
    - **Coach notes**: include (default) or leave out.
-   - **Languages**: options "{{languageNames}}, opens in the browser language" (default), "English
-     only" and "Italian only". Say that I can type another choice, for example "English and Italian,
-     opens in Italian".
+   - **Languages**: options "English and the language of my Garmin profile, opens in the profile
+     language" (default), "All: {{languageNames}}", "English only" and "Italian only". Say that I can
+     type another choice, for example "English and Italian, opens in Italian".
    - **Themes**: options "All 11 themes, opens in midnight" (default), "Midnight only" and "Paper
      only". Say that I can type other themes and the one it opens in: {{themes}}.
 3. Call `writeDashboard` with `preview` = true, `weeks` = {{weeks}} and the `path`. It writes nothing.
@@ -43,9 +43,9 @@ such a tool, ask the questions in chat as numbered lists, with the default first
 Use only numbers of the digest. **Never invent, interpolate or estimate missing values.** If a value
 is missing, write "n/a". If a call fails, say which one and why in one line.
 
-Do not write or change the page yourself. Settings need a page from the template: a page that Claude
-designed (layout freeform) cannot keep them.
+Do not write or change the page yourself. Settings need a page from the template: a page designed with
+layout freeform cannot keep them.
 
 Finish with two lines in chat: the path of the page with the command to open it (`open` on macOS,
 `xdg-open` on Linux, `start` on Windows), and the settings that the page keeps. Later updates keep
-the settings: for a page with another file name, ask Claude to update that file.
+the settings: for a page with another file name, ask your assistant to update that file.

package/prompts/training-dashboard-freeform.md

@@ -27,6 +27,10 @@ of `getDashboardData` with `weeks` = {{weeks}}, which has:
   `failedSections` is not empty, name those sections in chat: `zones` and `fitnessAge` are then null
   and `hrv` can have no rows. Their widgets show "n/a".
 - `notes`: the coach notes, a list of strings. The server escapes them as HTML.
+- `units`: the measurement system of my Garmin profile. The data is always metric (km, m, kg,
+  pace per km). Show every distance, pace, speed, elevation and weight in my units: `metric` km,
+  /km, km/h, m, kg; `statute_us` mi, /mi, mph, ft, lb; `statute_uk` mi, /mi, mph, m, lb. Without
+  `units`, use metric. Race names (5 km, 10 km, half marathon) stay as they are.
 
 You do not need to call `getDashboardData`: the field names above are all the page needs.
 

package/prompts/training-dashboard.md

@@ -10,6 +10,14 @@ Answer in my language.
    Training suggestions only, no medical advice. Plain text, in my language.
 3. Call `writeDashboard` again with the same `weeks` and the `notes`, without `layout`. The page keeps
    its layout.
+4. Tell me the languages of the page (`pageLanguages` of the result) and ask whether to add one.
+   If your client has a tool for questions with choices, use it, with "No" as the default and the
+   built-in languages that the page does not have: {{builtIn}}. Say that I can type any other
+   language.
+   - A built-in language: call `writeDashboard` with the same `weeks` and `notes`, and `settings` =
+     the `settings` of the last result, with `languages` = the codes of `pageLanguages` that are `en`
+     or built in, and the new code.
+   - Any other language: tell me to run the `dashboard-language` prompt with it.
 
 Use only numbers of the digest. **Never invent, interpolate or estimate missing values.** If a value
 is missing, write "n/a". If `sync.failedDays` is more than 0, name the dates in `sync.failedDates`.