enduraw-MCP

get_enduraw_activities_stats

Fetch aggregate Enduraw training statistics—total sessions, distance, time, observed vs estimated time, and time saved—for a chosen period to track overall training volume and efficiency.

Instructions

Fetches aggregate statistics across all training sessions recorded on Enduraw: total sessions, total distance (km), total time (h), observed vs estimated time breakdown, and time saved.

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

Input Schema

Name	Required	Description	Default
`period`	No	Time period to aggregate: '52w' (default), 'all', '12w', '4w'	52w

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Fetches' implies a read-only operation and the description names computed metrics with units, but it does not explicitly confirm read-only safety, data freshness, permissions, or response shape.

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?

The description is a single front-loaded sentence that states the action, scope, and returned metrics without filler. The metric list is useful and every phrase contributes to selection or expectation setting.

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?

For a low-complexity, one-parameter aggregate tool with no output schema, the description names the key returned metrics and enough scope to set expectations. It is slightly incomplete because it omits the period parameter's behavior and does not describe response structure beyond the metric list.

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?

The only parameter, period, is fully documented in the schema with its default and allowed values. The tool description does not mention period at all, so it adds no meaning beyond the high-coverage schema; baseline 3 is appropriate.

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 and resource: 'Fetches aggregate statistics across all training sessions recorded on Enduraw,' then lists the exact metrics returned. This clearly distinguishes an aggregate-stats tool from a sibling likely listing individual activities, though it does not explicitly name an alternative.

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 phrase 'aggregate statistics across all training sessions' implies this is for high-level totals rather than per-activity detail. However, it does not state when to use this over siblings like get_enduraw_activities or get_enduraw_matrix_summary, nor does it mention exclusions.

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