matrix-workouts-mcp

export_workout

Write a ride to disk as a lossless JSON export, including normalized telemetry and the original record. Returns the file path for large documents.

Instructions

Write one ride to disk as a lossless JSON export document — normalized telemetry plus the upstream record verbatim. Returns the path, not the contents, because the document is far too large to read into a conversation.

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": {
      "id": "<id>"
    },
    "name": "export_workout"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`path`	No	Directory or file path. Defaults to the cache directory.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden. It clearly reveals that the tool writes to disk, returns a path rather than file contents, and explains the size rationale. It could add details about overwrite behavior or file naming, but the core side effects and output behavior are well disclosed.

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?

Two tight sentences, front-loaded with the action and format, then a concrete behavioral clarification. Every sentence earns its place with no filler.

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?

The tool is simple, but with no output schema the description must explain return value and side effects, which it does by stating a path is returned and contents are intentionally omitted. Minor gaps remain around output file naming/extension and overwrite semantics, but an agent has enough to call it correctly.

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 description coverage is only 50%, and the tool description does not compensate. The 'id' parameter is only typed as a string with no explanation, and although the description mentions 'one ride', it never explicitly maps that to the id parameter. The 'path' parameter is already explained in the schema and gains no extra meaning.

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

Purpose5/5

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

The description states a specific action ('write one ride to disk'), a concrete resource outcome ('lossless JSON export document'), and the document's composition. It clearly differentiates from siblings like get_workout by explicitly saying it returns the path, not the contents.

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 implies the tool is for persisting a workout for later use and that it should not be used when contents are needed in conversation. However, it does not explicitly name an alternative tool or state when-not-to-use conditions, leaving routing to inference.

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

Deploy Server