enduraw-MCP

get_enduraw_physio_tests

Retrieve official Enduraw physiological test protocols, booking availability, and the runner’s computed benchmarks such as critical speed and cardiac efficiency.

Instructions

Comprehensive physiological testing hub: retrieves official Enduraw testing protocols (Flat VMA/Vc test, Incline VAM test, Lactate testing), booking availability, cognitive Stroop test status, AND all computed physiological benchmarks extracted from the runner's real history (Critical Speed, Slope VAM curve, Cardiac Efficiency, Post-effort Recovery Kinetics).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Retrieves' implies a read operation, but the description does not state permissions, rate limits, response shape, or whether all listed datasets are always returned together; it only lists content categories.

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

Conciseness3/5

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

The description is a single front-loaded sentence, but it is a dense run-on listing many disparate outputs. 'Comprehensive physiological testing hub' is filler, and the long parenthetical list makes it harder to scan than necessary.

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 zero-parameter read tool with no output schema, the description lists the major return categories (protocols, availability, cognitive status, benchmarks). However, it does not clarify how those categories are packaged or whether the response is large and always fully populated, leaving an agent with only moderate confidence about what to expect.

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 has zero parameters, so the baseline is 4. There are no parameter semantics to document, and the description does not need to compensate for an input schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves several physiological testing artifacts, but it is a broad grab-bag (protocols, booking availability, cognitive status, and benchmarks) rather than a single clear resource. It does not distinguish itself from siblings such as get_enduraw_cardio_efficiency or get_enduraw_slope_and_cadence, which appear to overlap with some of the listed benchmarks.

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 explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer it is for physiological testing and benchmarking, but it is not told when to choose this hub over the many specialized sibling tools.

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