matrix-workouts-mcp

compare_workouts

Compare multiple rides side by side across all derived metrics, such as power, cadence, resistance, and heart rate, so you can see how today's session compares against prior workouts.

Instructions

Two or more rides side by side on every derived number. Use it for 'how did today compare to last Tuesday' rather than calling get_workout repeatedly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "compare_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It implies comparison but does not state side effects, performance, output shape, or limitations. The 'derived number' phrase is ambiguous and adds little behavioral clarity.

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 short and front-loads the core concept, with a usage example embedded. It is concise, though the phrase 'every derived number' is odd and slightly wastes the second sentence's potential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter and no annotations or output schema, the description leaves key details missing: what 'ids' means, what comparison metrics are returned, and any constraints. The guidance to avoid get_workout is helpful but insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not explain the 'ids' parameter beyond the schema. It does not clarify expected IDs, count limits, or formatting, so the description fails to compensate for the lack of schema documentation.

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 'Two or more rides side by side on every derived number' conveys a compare action with specific intent, but 'derived number' is vague and doesn't clearly state what is compared (e.g., metrics, workouts). It does distinguish from siblings by advising not to call get_workout repeatedly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a concrete use case ('how did today compare to last Tuesday') and explicitly contrasts with an alternative ('rather than calling get_workout repeatedly'). It lacks when-not-to-use or other alternatives, but the context is clear.

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

Deploy Server