Skip to main content
Glama

get_training_effect

Read-only

Retrieves aerobic and anaerobic training effect for a specific Garmin activity, falling back to activity list search when the details endpoint returns HTTP 403.

Instructions

Get training effect data for a specific activity.

    Uses activity details first. If Garmin returns HTTP 403 for that
    endpoint (seen on valid, recent activities), falls back to activity
    list search, which still includes aerobic/anaerobic training effect.

    Args:
        activity_id: ID of the activity to retrieve training effect for
    

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_training_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish this as a safe read with open-world network access, and the description usefully adds that it may silently fall back to an activity-list search when the details endpoint returns HTTP 403 - so results can come from a different source with the same fields in practice. It does not say anything about the shape or reliability of the returned data, latency, or whether the fallback path yields reduced fidelity.

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 purpose sentence followed by a short fallback note and an Args block; no filler. The docstring-style Args section is slightly redundant since the prose already implies the parameter, but it costs almost nothing.

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

Completeness3/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 should convey what 'training effect data' contains; the only hint is the parenthetical mention of aerobic/anaerobic training effect buried in the fallback sentence. Safe-read behavior is covered by annotations, but the return content and fallback's effect on completeness are under-described.

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% and the description only restates that activity_id identifies the activity whose training effect is retrieved, adding no format, source, or sourcing detail beyond the schema's integer title. For a single obvious identifier this is minimally adequate rather than compensating.

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?

Names a specific verb and resource ('Get training effect data') plus a clear scope ('for a specific activity'), which distinguishes it from generic activity fetchers like get_activity or get_activity_fit_data. It stops short of explicitly naming a sibling it replaces.

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

Usage Guidelines2/5

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

The description explains the tool's internal endpoint fallback, not when an agent should call this instead of get_activity, get_activity_fit_data, or other training-metric siblings. No exclusions, prerequisites, or alternative-selection guidance are given.

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