io.github.matisdsp/fartlek

Overview Schema Source Related Servers Discussions Admin

garmin_log

Idempotent

Log subjective training data like RPE, wellness scores, and notes to calculate sRPE load and readiness. Flag illness or injury and resolve when healed.

Instructions

Subjective data the watch cannot capture: session RPE (1-10), Hooper wellness (fatigue, soreness, stress, mood, sleep quality, each 1-7), and notes — especially illness or injury (set flag; resolve when healed). Feeds sRPE load and caps the readiness verdict. Ask for RPE after discussing a session if missing.

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

Input Schema

Name	Required	Description
`rpe`	No
`date`	No	YYYY-MM-DD, default today
`flag`	No
`mood`	No
`note`	No
`stress`	No
`fatigue`	No
`soreness`	No
`activity_id`	No
`resolve_flag`	No
`sleep_quality`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses important downstream effects: the data 'feeds sRPE load and caps the readiness verdict.' It also explains the flag lifecycle ('set flag; resolve when healed'), adding behavioral context far beyond what annotations alone provide.

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 three sentences, with the core purpose front-loaded in the first phrase. Every sentence adds value: field enumeration, downstream consequences, and a specific interaction guideline. No filler or redundant restatement of the tool name.

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

Completeness5/5

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

For an 11-parameter, presumably write-oriented tool, the description covers what to log, the exact scales, the flag lifecycle, the effect on load/readiness, and when to prompt for missing data. The existence of an output schema reduces the need to describe return values, and the description stands well alongside sibling tools.

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

Parameters5/5

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

Despite the very low schema description coverage (9%), the description compensates thoroughly by enumerating all key parameters with their scales: RPE 1-10, Hooper wellness dimensions (fatigue, soreness, stress, mood, sleep quality) each 1-7, notes, and flags. It also clarifies the resolve_flag behavior and the expected values for wellness parameters.

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 opens with 'Subjective data the watch cannot capture,' clearly identifying the tool's resource and scope: logging RPE, Hooper wellness, notes, and flags. It distinguishes itself from sibling tools by contrasting with objective watch-captured data, and names concrete fields with ranges.

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?

The description gives explicit guidance for when to log RPE ('Ask for RPE after discussing a session if missing') and when to set/resolve illness or injury flags. It implies the tool is for subjective data only, which differentiates it from objective sibling tools, but it does not explicitly name alternatives or state when not to use it.

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

Deploy Server