Skip to main content
Glama

get_running_tolerance

Read-only

Retrieve Garmin's running load capacity for a specific day, including tolerance, acute load, distance, and load ratio to compare how intensity affects each kilometer.

Instructions

Get Running Tolerance for a single day.

    Returns Garmin's running load capacity model: how much running load the
    athlete can currently absorb (tolerance), the intensity-adjusted load
    their recent runs have produced (acute load), and the raw distance behind
    that load. All three are expressed in km so they're directly comparable —
    `load_ratio` (acute_load_km / distance_km) quantifies how much intensity
    is inflating the cost of each kilometer run.

    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_running_tolerance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful behavioral context: it defines the three returned quantities, states their common unit (km) and why they're comparable, and explains the derived load_ratio formula. It omits failure modes such as missing data for days without runs, which slightly holds it back.

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 one-line purpose, then a compact explanation of the returned model before the argument spec. The docstring-style Args block is somewhat redundant given the single parameter is already named in the schema, but overall there is little waste.

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?

There is no output schema, so the description carries the full burden of explaining return values — and it does so thoroughly with definitions, units, and the derived ratio. For a one-parameter read tool that is nearly complete; only edge-case behavior for absent or insufficient data is unaddressed.

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 0% — the single date parameter has no description at all — so the description must compensate, and it does by specifying the exact YYYY-MM-DD format. That is the critical missing piece for correct invocation. It does not address timezone or permissible date range, which would have pushed this higher.

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

Purpose4/5

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

The description uses a specific verb+resource combination ("Get Running Tolerance") and scopes it to "a single day," which implicitly distinguishes it from the trend sibling. It goes further by naming the underlying model (load capacity vs. acute load) so the agent understands what the resource actually is. It stops short of explicitly naming the trend tool it contrasts with.

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

Usage Guidelines3/5

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

The "for a single day" scoping plus the sibling name get_running_tolerance_trend implies the split between point-in-time and trend queries, but the description never states when to pick this over the trend variant or what the athlete-type prerequisites are (e.g., does it apply to non-runners?). Usage is implied rather than stated.

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