enduraw-MCP

get_enduraw_cardio_efficiency

Retrieve cardiac efficiency versus speed across pace intervals, including median heart rate, Q25/Q75 dispersion, and post-effort recovery metrics for aerobic pacing analysis.

Instructions

Retrieves cardiac efficiency vs speed ('Que coute votre allure en battements ?') across 66 speed/pace intervals with median HR, Q25/Q75 dispersion, and post-effort heart rate recovery metrics.

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

Input Schema

Name	Required	Description	Default
`max_speed_kmh`	No	Optional maximum speed in km/h (e.g. 15.0)
`min_speed_kmh`	No	Optional minimum speed in km/h (e.g. 8.0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

B3.2/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 burden. 'Retrieves' implies a safe read, and the phrase about 66 intervals plus dispersion metrics discloses the shape of the result, but nothing is said about data-coverage requirements, behavior when no HR data exists, or response size.

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?

One front-loaded sentence with no filler; the core resource and the returned fields are stated immediately. The embedded French tagline is decorative rather than informative and marginally dilutes the sentence.

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?

With no output schema, the description usefully names the returned statistics (median, quartiles, recovery), which is the main thing an agent cannot see elsewhere. However, for an analytics tool with no annotations, it omits prerequisites, empty-result behavior, and routing guidance to sibling tools.

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 100%, so min_speed_kmh and max_speed_kmh are already documented with units and examples. The description mentions 66 speed/pace intervals but does not explain that the two parameters narrow that range, adding no meaning beyond the schema. Baseline 3 applies.

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 ('Retrieves') plus a clearly-named resource ('cardiac efficiency vs speed') and enumerates the returned measures (median HR, Q25/Q75, post-effort recovery). An agent can tell it apart from get_enduraw_cardio_zones or get_enduraw_slope_and_cadence, though the description never explicitly contrasts them.

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?

There is no statement of when to call this versus the many sibling analysis tools (cardio_zones, performance_profile, activity_analysis), and no prerequisites such as needing recorded activities with HR data. The reader must infer applicability entirely from the resource name.

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