Skip to main content
Glama

showDashboard

Displays the Garmin training dashboard in chat, rendering a selected or preset page with current data for the chosen weeks. Use it to view layouts, widgets, and settings without writing a page file.

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 no page file, but updates the data cache and the saved .FIT files as getDashboardData does, 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

NameRequiredDescriptionDefault
pathNoThe .html file; relative paths are inside the data dir
weeksNoWeeks to cover, default the page's or 12, max 52

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that no page file is written, that the data cache and saved .FIT files are updated as getDashboardData does, and that coach notes are absent. It also names the return payload (page path, data digest, page settings), which is unusually complete for a tool lacking an output schema.

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?

Two sentences with zero filler; the primary action is front-loaded before the assistant-conditional details. The second sentence is long and heavily nested with parentheticals, which slows parsing, but every clause (side effects, absent notes, return values, alternative) carries distinct information.

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?

For a no-annotation tool with no output schema, the description covers side effects, persistence behavior, return values, defaults, and the routing alternative to writeDashboard. Nothing an agent needs in order to decide between this and its sibling is missing.

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%, so the baseline is 3, but the description adds genuine meaning: it supplies the actual default for `path` (<data-dir>/garmin-dashboard.html), which the schema only gestures at with 'relative paths are inside the data dir', and clarifies that `weeks` controls the window of new data. The fallback-to-'page's or 12' behavior is left implicit in the text but is present in the schema.

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?

The opening clause gives a specific verb and resource ('Shows the training dashboard in the chat') and immediately scopes it to assistants that render MCP Apps, with explicit contrast against writeDashboard for other assistants. An agent can distinguish it from getDashboardData and writeDashboard without opening any schema.

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?

The description states the condition for use (assistants that show MCP Apps) and the negative case ('Other assistants show only this reply: there, writeDashboard writes the page as a file'), naming the alternative explicitly. Both branches and the fallback tool are spelled out, leaving nothing to inference.

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