Skip to main content
Glama

set_fit_download_dir

Set and save the default folder for downloaded Garmin activity files, letting future downloads use that path without prompting each time.

Instructions

Set and persist the default directory for downloaded activity files.

    Stores the absolute path in a small JSON config file
    (~/.garminconnect_fit_config.json, overridable via GARMIN_FIT_CONFIG) so
    download_activity_file can save files without asking again.

    Args:
        path: Directory where activity files (.fit/.gpx/.tcx/.csv) are saved.
              Pass the current working directory to keep files where the
              server runs.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "set_fit_download_dir"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the path is written to a JSON config file at ~/.garminconnect_fit_config.json, that location is overridable via GARMIN_FIT_CONFIG, and the setting persists across calls. Unexplained are validation details (whether the directory must already exist, whether relative paths are accepted) which matter because the parameter is silently treated as absolute.

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?

The intent is front-loaded in the first sentence, followed by the persistence mechanism and a short Args block. The indented multi-line Args formatting is slightly verbose for one parameter but every line conveys usable information.

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

Completeness4/5

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

For a one-parameter tool with no output schema and existing annotations, the description covers the write target, persistence location, override mechanism, and consumer relationship. Only the validation/error semantics of the path argument are left unstated.

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

Parameters3/5

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

Schema coverage is 0% and the single 'path' parameter is a bare string, so the description must carry the load. It explains that path is the directory where .fit/.gpx/.tcx/.csv files land and suggests passing the cwd, but it does not clarify relative-vs-absolute handling or whether the directory is created if missing.

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: 'Set and persist the default directory for downloaded activity files.' It also names the downstream consumer (download_activity_file), so an agent knows exactly what this controls and can distinguish it from the download/read siblings.

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

Usage Guidelines4/5

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

Usage context is clear: call this so download_activity_file can save files without prompting again, and pass the current working directory to keep files beside the server. It does not state when NOT to use it (e.g. when a config already exists) or whether re-calling overwrites silently, so it falls short of explicit when/when-not guidance.

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

Deploy Server

Other Tools