enduraw-MCP

get_enduraw_cardio_zones

Retrieves Karvonen heart rate zones Z1-Z5 with time and share spent per zone across training history, resting HR, and max HR for training intensity analysis.

Instructions

Retrieves Karvonen heart rate zones (Z1 to Z5), total time and share spent in each zone across training history, resting HR, and max HR.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_enduraw_cardio_zones"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful scope — the data spans 'training history' and is a retrieval (read-only implied) — but it says nothing about permissions required, whether zones are computed against current or historical resting/max HR, or how large the result set can be.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the core resource (Karvonen zones) and then enumerates the returned content. No filler, no restatement of the tool name, nothing padded.

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?

With no output schema, the description must convey what comes back, and it does: zone band, time and share per zone, resting HR, max HR. For a zero-parameter read tool that is close to sufficient; the only gap is the absence of any note on how zones are derived or what happens when HR data is incomplete.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies a fixed, unfiltered query with no options to specify.

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?

Specific verb plus resource: it names Karvonen heart rate zones Z1–Z5 and the metrics returned (time and share per zone, resting HR, max HR). An agent can tell this apart from adjacent tools like get_enduraw_cardio_efficiency or get_enduraw_performance_profile by the Karvonen-zone framing. It does not explicitly state how it differs from those siblings, which keeps it at 4.

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 says what is retrieved but never when to reach for it, when not to, or which sibling to prefer for a heart-rate analysis question. With 23 sibling tools in this family, that routing guidance is exactly what is missing.

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