Skip to main content
Glama

log_garmin_readiness

Idempotent

Record the Garmin Training Readiness score locally to calibrate readiness estimates; log it whenever a user mentions their readiness, close to when it was read.

Instructions

Record the Training Readiness score Garmin shows (0-100), stored locally, so the estimate calibrates to it (an offset at first, a fitted slope from 4 scores). Log it whenever the user mentions their Garmin readiness. Readiness drops after workouts, so log it close to when it was read.

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": {
      "score": "<score>"
    },
    "name": "log_garmin_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNotoday
noteNo
scoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: local storage, the calibration model (offset at first, fitted slope from 4 scores), and the decay-after-workout rationale for timing. It stops short of describing what is returned or how a duplicate/overwritten entry behaves.

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?

Four short sentences, front-loaded with what it records, then the storage/calibration rationale, then usage timing. Efficient overall, though the calibration parenthetical is more detail than an invocation decision strictly needs.

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?

With no output schema and clear annotations, the description covers purpose, timing, and downstream effect well enough to call it. The gap is the undocumented 'day' and 'note' parameters, which leaves an agent guessing about backfilling past dates and attaching context.

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 0%, so the description must carry parameter meaning and it largely does not. It conveys the score's valid range (0-100) but says nothing about 'day' (defaults to 'today') or 'note', leaving two of three parameters undocumented anywhere.

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?

States a specific verb (record) and resource (the Garmin Training Readiness score, 0-100) and adds that it is stored locally. The calibration clause separates it from read-only siblings such as readiness_history, so an agent can tell which one to pick without opening the schema.

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?

Gives an explicit trigger ('whenever the user mentions their Garmin readiness') and a timing constraint ('log it close to when it was read' because readiness drops after workouts). No 'when not to use' or named alternative is given, which keeps it just short of a 5.

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