@indaco/garmin-personal-mcp 0.2.0 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indaco/garmin-personal-mcp",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "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-language.md

@@ -10,6 +10,9 @@ Add {{language}} to my Garmin training dashboard. Use the tools of the `garmin-p
    The code is the language code, for example `de`, `fr` or `pt-BR`. Send at most 150 texts in one
    call.
 4. If the reply lists `missing` texts for the language, translate them and call again.
+5. If `customWidgets` of the first reply has widgets with `texts`, translate their English texts
+   (`texts.en`) the same way, and call `editDashboard` with `widgetTexts` =
+   { "<widget id>": { "<code>": { "<key>": "<text>", ... } } }{{pathArgument}}.
 
 Finish with one line in chat: the language code, and that the Language menu of the page shows the
 language after a reload.

package/prompts/dashboard-setup.md

@@ -40,12 +40,30 @@ such a tool, ask the questions in chat as numbered lists, with the default first
    language. Then call `writeDashboard` again with the same `weeks`, `path` and the `notes`, without
    `settings`: the page keeps them.
 
+If a `writeDashboard` result has `missingWidgetTexts`, call `editDashboard` with the same `path` without
+changes, translate the English texts of those widgets (`customWidgets[].texts.en`) into the listed
+languages, keeping each `{placeholder}`, and call `editDashboard` with `widgetTexts` =
+{ "<widget id>": { "<code>": { "<key>": "<text>", ... } } }.
+
 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 designed with
 layout freeform cannot keep them.
 
+Automatic refresh: call `scheduleDashboardRefresh` without arguments. If its `pages` do not have
+the `path` of the page, ask me once whether to update the page automatically. If your client has a
+tool for questions with choices, use it: "No" (the default), every day at 07:00, weekdays at 07:00,
+every Monday at 07:00. Say that I can also tell you when in my own words, in any language, for
+example "Monday and Thursday at 18" or "the first day of each month at 8". If `scheduled` is true,
+the schedule is for all the pages: offer `cron`, in words, as the first choice after "No". Say that
+each automatic refresh replaces the data and removes the coach notes, and that the computer must be
+on. On a yes, turn the answer into a cron expression and call `scheduleDashboardRefresh` with `cron`
+and the `path` of the page. Tell me the schedule and the `next` runs of the reply in my language, in
+one line.
+
 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 your assistant to update that file.
+If the last reply has `missingProfileLanguage`, add one line: my Garmin profile uses that language,
+the page has no texts in it and shows English, and the `dashboard-language` prompt adds the language.

package/prompts/dashboard-widget.md

@@ -4,13 +4,18 @@ MCP server. Answer in my language.
 1. Call `editDashboard` with no other arguments{{pathArgument}}. Read `widgetApi` (how a widget works), `catalogue` (the
    built-in widgets) and `customWidgets`. If there is no dashboard, call `writeDashboard`{{pathWith}} first.
 2. If a built-in widget already shows this, name it, add it with `place`, and stop.
-3. Write the widget as `widgetApi` says: the body of a function (el, ctx), a short id and a title.
+3. Write the widget as `widgetApi` says: the body of a function (el, ctx), a short id, a title, and
+   `texts` with every text it shows, in English and in each language of `pageLanguages`.
    Use only values from `ctx.data`. Show `ctx.fmt.na` for a missing value. Label an estimate as one.
    **Never invent, interpolate or estimate missing values.**
 4. Call `editDashboard` with `widgets` = [the widget] and `place` = [{ board, widget, span }] for the
    board that fits the idea (`all` if no board fits){{pathArgument}}.
 5. If the reply has an error, fix the widget and call `editDashboard` again{{pathWith}}, at most 2 times.
 
+The server also saves the widget in my widget library, so each new page gets it. To remove a
+widget from this page only, use `removeWidgets`; to remove it from the library too, use
+`forgetWidgets`.
+
 You cannot open the page, so the widget is not tested. A widget that fails shows its error in its own
 tile, and the rest of the page works.
 

package/prompts/training-dashboard-freeform.md

@@ -309,5 +309,16 @@ to phone width (the tab bar scrolls horizontally, the page does not). Make the t
 keyboard. Put tooltips on every chart and units on every axis. Use your own visual identity: no
 third-party app names, logos or brand colours.
 
+Automatic refresh: call `scheduleDashboardRefresh` without arguments. If its `pages` do not have
+the `path` of the page, ask me once whether to update the page automatically. If your client has a
+tool for questions with choices, use it: "No" (the default), every day at 07:00, weekdays at 07:00,
+every Monday at 07:00. Say that I can also tell you when in my own words, in any language, for
+example "Monday and Thursday at 18" or "the first day of each month at 8". If `scheduled` is true,
+the schedule is for all the pages: offer `cron`, in words, as the first choice after "No". Say that
+each automatic refresh replaces the data and removes the coach notes, and that the computer must be
+on. On a yes, turn the answer into a cron expression and call `scheduleDashboardRefresh` with `cron`
+and the `path` of the page. Tell me the schedule and the `next` runs of the reply in my language, in
+one line.
+
 Finish with two lines in chat: what is in the dashboard with the path of the page and the command
 to open it (`open` on macOS, `xdg-open` on Linux, `start` on Windows), and anything that was missing.

package/prompts/training-dashboard-update.md

@@ -11,10 +11,22 @@ tools of the `garmin-personal` MCP server. Answer in my language.
 4. If the reply lists `languages` with `missing` texts, translate them as the `dashboard-language`
    prompt says, and call `editDashboard`{{pathWith}} to save them.
 
+If a `writeDashboard` result has `missingWidgetTexts`, call `editDashboard`{{pathWith}} without
+changes, translate the English texts of those widgets (`customWidgets[].texts.en`) into the listed
+languages, keeping each `{placeholder}`, and call `editDashboard` with `widgetTexts` =
+{ "<widget id>": { "<code>": { "<key>": "<text>", ... } } }{{pathArgument}}.
+
 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.
 
+If the reply has `missingProfileLanguage`, add one line: my Garmin profile uses that language, the
+page shows English, and the `dashboard-language` prompt adds the language.
+
 Finish with two lines in chat: the period that the dashboard covers now, with the number of new
 activities (`sync.newActivities`), and anything that was missing. If `sync.failedDays` is more than
 0, name the dates in `sync.failedDates`. If `sync.failedSections` is not empty, name those sections
 (HR zones, fitness age, HRV) and say that they show as "n/a".
+
+Call `scheduleDashboardRefresh` without arguments. If its `pages` do not have this page, add one
+line: you can update the page automatically when I ask, in my own words, for example "update it
+every Monday at 7".

package/prompts/training-dashboard.md

@@ -2,15 +2,26 @@ You are a data-minded endurance coach. Using the tools of the `garmin-personal`
 personal **training + recovery dashboard** for the last **{{weeks}} weeks** (today is {{today}}).
 Answer in my language.
 
-1. Call `writeDashboard` with `weeks` = {{weeks}} and `layout` = "{{layout}}". The server gets the
+1. First ask two questions. If your client has a tool for questions with choices, use it; without
+   one, ask in chat as numbered lists, with the default first:
+   - **Title**: options "Keep the title" (default: the title of the page, "{{title}}" for a new
+     page) and "Type my own".
+   - **Headline** (the line under the title): options "Keep the headline" (default: the headline of
+     the page, "{{headline}}" for a new page) and "Type my own".
+   When I choose "Type my own" and give no text, ask for the text in chat.
+2. Call `writeDashboard` with `weeks` = {{weeks}} and `layout` = "{{layout}}". The server gets the
    data, writes the page from its template, and returns the path of the page and a digest of the
    data. An existing page stays as a `.bak` file.
-2. Write at most 5 coach notes from the digest. Each note names a specific number of the digest, for
+3. Write at most 5 coach notes from the digest. Each note names a specific number of the digest, for
    example "load ratio 1.18 while HRV was under its weekly average on 3 of the last 7 nights".
    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.
+4. Call `writeDashboard` again with the same `weeks` and the `notes`, without `layout`. The page keeps
+   its layout. If I typed my own title or headline, also give `settings` = the `settings` of the
+   last result with `title` and `headline` set to my texts: the other settings of the page stay.
+5. If the result has `missingProfileLanguage`, say first that my Garmin profile uses that language,
+   that the page has no texts in it yet, so the page shows English, and that you can add it.
+   Make that language the default of the question below instead of "No".
+   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.
@@ -19,6 +30,11 @@ Answer in my language.
      or built in, and the new code.
    - Any other language: tell me to run the `dashboard-language` prompt with it.
 
+If a `writeDashboard` result has `missingWidgetTexts`, call `editDashboard` without
+changes, translate the English texts of those widgets (`customWidgets[].texts.en`) into the listed
+languages, keeping each `{placeholder}`, and call `editDashboard` with `widgetTexts` =
+{ "<widget id>": { "<code>": { "<key>": "<text>", ... } } }.
+
 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`.
 If `sync.failedSections` is not empty, name those sections (HR zones, fitness age, HRV) and say that
@@ -27,5 +43,16 @@ they show as "n/a". If a call fails, say which one and why in one line.
 Do not write or change the page yourself, and do not call `getDashboardData`: the digest has what the
 notes need.
 
+Automatic refresh: call `scheduleDashboardRefresh` without arguments. If its `pages` do not have
+the `path` of the page, ask me once whether to update the page automatically. If your client has a
+tool for questions with choices, use it: "No" (the default), every day at 07:00, weekdays at 07:00,
+every Monday at 07:00. Say that I can also tell you when in my own words, in any language, for
+example "Monday and Thursday at 18" or "the first day of each month at 8". If `scheduled` is true,
+the schedule is for all the pages: offer `cron`, in words, as the first choice after "No". Say that
+each automatic refresh replaces the data and removes the coach notes, and that the computer must be
+on. On a yes, turn the answer into a cron expression and call `scheduleDashboardRefresh` with `cron`
+and the `path` of the page. Tell me the schedule and the `next` runs of the reply in my language, in
+one line.
+
 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 anything that was missing.{{layoutNote}}