Garmin Personal MCP

Overview Schema Source Related Servers Discussions Admin

showDashboard

Read-only

Displays a Garmin training dashboard in chat for MCP Apps, using a specified HTML page or preset layout with recent weeks of training data.

Instructions

Shows the training dashboard in the chat, in assistants that show MCP Apps: the page of path (default /garmin-dashboard.html) with its layout, custom widgets, languages and settings, or the preset page when there is none, with new data of the last weeks weeks. Writes nothing and has no coach notes. Returns the page path, the digest of the data and the page settings. Other assistants show only this reply: there, writeDashboard writes the page as a file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "showDashboard"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No	The .html file; relative paths are inside the data dir
`weeks`	No	Weeks to cover, default the page's or 12, max 52

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.0Nov 2, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint/openWorldHint it discloses that the tool writes nothing, emits no coach notes, falls back to a preset page when `path` is absent, defaults the path to <data-dir>/garmin-dashboard.html, and reports the page path, data digest and settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and free of filler, but the first sentence is a long run-on with nested parentheticals, and the closing contrast with writeDashboard is phrased awkwardly enough to need a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still names what comes back (page path, data digest, settings) and covers the environment caveat, defaults and fallback behavior, leaving nothing an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents `weeks` (default from page or 12, max 52), so the schema carries most weight; the description adds real value by giving the default file location and the preset-page fallback for a missing `path`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Shows the training dashboard in the chat') plus the rendering medium (MCP Apps page of `path`), and explicitly names the sibling that does the file-writing job instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the condition for use ('in assistants that show MCP Apps') and the exclusion with an alternative ('Other assistants show only this reply: there, writeDashboard writes the page as a file'), so the agent can route between the two without opening either schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.