enduraw-MCP

get_enduraw_activities

Fetches recent Enduraw activities with duration, distance, weather conditions, and analysis readiness. Filter by period or analyzed-only sessions to review training data.

Instructions

Fetches recent activities synced to Enduraw with duration, distance, weather conditions (temp, wind), and analysis readiness status. Supports period filtering ('52w', 'all', '12w', '4w') and filtering for analyzed sessions.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Number of activities to retrieve (default: 10, max: 100)
`period`	No	Time period ('52w', 'all', '12w', '4w')	52w
`analyzed_only`	No	If true, only return activities with completed deep analysis (analysis_ready: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully implies a read-only fetch of synced activities and names the returned data fields, but it does not cover sorting, pagination beyond the schema's limit, permissions, or any other operational behavior.

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?

The description is two compact sentences and is front-loaded with the core action and returned data. It is efficient, though it slightly repeats filter values already present in the schema.

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?

For a low-complexity read tool with three optional parameters and no output schema, the description gives useful information about returned fields and filters. It still lacks sibling-tool guidance and does not describe the response structure or pagination behavior, leaving some selection and invocation gaps.

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 the input schema already documents limit, period, and analyzed_only. The description restates the period values and analyzed-session filtering but adds no additional parameter meaning beyond what the schema provides.

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 states a specific verb and resource: 'Fetches recent activities synced to Enduraw.' It also names returned data fields such as duration, distance, weather conditions, and analysis readiness. However, it does not explicitly distinguish this tool from siblings like get_enduraw_activities_stats, get_enduraw_activities_map, or get_enduraw_activity_analysis.

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 description indicates that the tool supports period filtering and filtering for analyzed sessions, which implies usage for listing recent activities under those conditions. It does not explain when to choose this tool instead of sibling tools for stats, maps, or detailed activity analysis.

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