Skip to main content
Glama

get_training_load_balance

Read-only

Retrieve Garmin Load Focus for a date to assess whether trailing-month training load is balanced across aerobic low, aerobic high, and anaerobic bands, with status versus target ranges.

Instructions

Get Garmin's Load Focus — the distribution of the trailing-month training load across Aerobic Low, Aerobic High, and Anaerobic intensity bands, plus the system's feedback phrase (e.g. AEROBIC_HIGH_SHORTAGE, BALANCED, ANAEROBIC_SHORTAGE).

    Use this to assess whether the athlete's training mix is balanced or
    deficient in a particular intensity band. Each band reports its load
    alongside Garmin's target range; a `status` of "below", "within", or
    "above" is computed from the load relative to that range.

    Garmin reports Load Focus per device. The primary activity tracker's
    record is used when it can be identified; `load_device_id` and
    `load_device_name` say which device the numbers came from.

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_training_load_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description goes further by disclosing the trailing-month window, that Garmin reports Load Focus per device, that the primary activity tracker's record is preferred when identifiable, and how the `status` value is derived (load relative to target range) — all behavior an agent could not infer from annotations.

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 purpose is front-loaded in the first sentence, then structured into usage, per-device caveat, and an Args block. Slightly verbose with some restatement (the feedback-phrase examples and the band explanation overlap), but every paragraph contributes orienting 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?

With no output schema, the description takes on the burden of explaining returns and does so fully: the three bands, their load-vs-target-range comparison, the computed `status` values, the feedback phrase, and the `load_device_id`/`load_device_name` provenance fields. An agent has everything needed to call it and interpret the result.

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 description coverage is 0% with a single required `date` parameter, so the description must carry the load. It does supply the format (YYYY-MM-DD), but never says what the date anchors — presumably the end of the trailing-month window — or what happens for dates without data. Partial compensation for a low-coverage 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?

States a specific resource (Garmin's Load Focus) and enumerates exactly what is returned — trailing-month load split across Aerobic Low, Aerobic High, and Anaerobic bands plus the feedback phrase. The band-level framing is concrete enough that an agent can tell it apart from sibling tools like get_training_load_trend or get_training_status without opening a schema.

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?

"Use this to assess whether the athlete's training mix is balanced or deficient in a particular intensity band" gives a clear selection context tied to a real decision. It stops short of naming alternatives (e.g. the trend tool) or stating when this tool is the wrong choice, so it earns a 4 rather than a 5.

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