Skip to main content
Glama

rate_workout

Idempotent

Stores the athlete's reported effort rating (1–10) and optional feel note in a workout session file, preserving Apple's own rating unless an explicit override is requested.

Instructions

Stores the effort the athlete told you (1 to 10) and an optional feel note in the session file, marked effort_source ai. Call it only after the athlete told you the number; Apple's own rating wins unless the athlete asks to change it (then pass override true).

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>",
      "effort": "<effort>"
    },
    "name": "rate_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkout id (full UUID or its first 8 characters) or file name.
feelNoShort free-text note, e.g. "legs heavy, breathing fine". Omit to keep the existing note.
effortYesEffort 1 (trivial) to 10 (all out), exactly as the athlete said it.
overrideNoSet true only when the athlete asks to replace their own rating from Apple (a file with effort_source "apple" is otherwise left alone). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. Beyond that, the description discloses the write target (session file), the provenance marker written (effort_source ai), and the important gating rule that an existing Apple-sourced rating is left alone unless override is true. It does not say what is returned or what happens on an out-of-range effort, but the safety-relevant behavior is well covered and consistent with the annotations.

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 sentences, both load-bearing: the first establishes the write and its provenance marker, the second carries the precondition and the override rule. Front-loaded with the action and free of restated name/title material.

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?

There is no output schema, and the description supplies what an agent needs for a mutation tool: when it may be called, what it writes, what it refuses to overwrite, and how to force an overwrite. Nothing about correct invocation is missing given the fully described schema.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds decision-level meaning for parameters the schema only describes mechanically: it frames effort as the number the athlete verbalized (not a computed value) and explains the precise condition under which override should be set to true, which is the one parameter an agent could plausibly get wrong.

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 states a specific verb and resource: it stores the athlete's effort (1-10) plus an optional feel note into the session file, stamped effort_source ai. That is unambiguous against the read-only siblings (get_workout, list_workouts, etc.), though it never explicitly names a contrasting tool or forgoes it.

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

Usage Guidelines5/5

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

It gives an explicit precondition ('Call it only after the athlete told you the number'), an explicit when-not ('Apple's own rating wins'), and the exact escape hatch for the exception ('the athlete asks to change it — then pass override true'). Nothing about selecting this tool is left to inference.

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