Skip to main content
Glama

get_endurance_score

Read-only

Retrieves endurance performance scores for a specified date range from Garmin Connect, helping users track and compare trends over time.

Instructions

Get endurance score data between dates

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End 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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_endurance_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this a non-destructive, read-only, open-world read, so the safety profile is covered. The description adds only the temporal scoping constraint and says nothing about what is returned (per-day values, units, aggregation), rate limits, or auth needs — nothing beyond the annotation surface.

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?

Short and front-loaded, with the purpose stated before the arguments. The Google-style 'Args:' block is slightly ceremonial for two parameters but each line carries real format information, so there is little waste.

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

Completeness2/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 carries the burden of explaining the return value, and it does not — an agent cannot know whether it gets a single score, a daily series, or nested records. For a data-retrieval tool whose result shape is undocumented, the definition is under-specified.

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% (parameters carry only titles), so the description must compensate; it does supply the YYYY-MM-DD format for both start_date and end_date, which the schema lacks. However, it does not state whether bounds are inclusive, timezone handling, allowed range, or ordering — so compensation is only partial.

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?

States a specific verb and resource: retrieve 'endurance score data' bounded 'between dates'. An agent can tell what is fetched, though 'endurance score data' is not described in terms of granularity or content, and no sibling (e.g. get_hill_score) is referenced to disambiguate.

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 required date range is implied by 'between dates', but there is no explicit when-to-use guidance, no exclusions, and no named alternative among the many score-related siblings. The agent must infer usage entirely from the tool name.

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