Skip to main content
Glama

training_summary

Read-onlyIdempotent

Summarizes Apple Health workouts by ISO week, showing sessions, time, distance, heart rate, easy-zone share, effort, cardiac cost trend, and sport volume.

Instructions

Per ISO week: sessions, time, distance, average heart rate, easy-zone share, mean effort (any source) and the cardiac cost trend (heart beats per 100 m at the best freestyle 100 pace, lower is better), plus volume by sport.

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

Input Schema

NameRequiredDescriptionDefault
weeksNoHow many ISO weeks (ending this week), default 8, max 104.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), so the description's job is interpretive context, and it delivers: it defines the cardiac cost trend in concrete units and directionality ('heart beats per 100 m at the best freestyle 100 pace, lower is better') and clarifies 'mean effort (any source)', which an agent could not derive from structured fields alone. What it omits is whether output is a week-indexed series and what happens with no activity in a week.

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?

One sentence, front-loaded with the 'Per ISO week' grouping key before the metric list, with the only parenthetical reserved for the one metric that genuinely needs explanation. Nothing is wasted and nothing important trails.

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?

For a read-only, one-parameter aggregator with no output schema, the description does the heavy lifting of listing returned metrics, which is the right call. It still leaves the response shape (a list of ISO weeks vs. a single aggregate) and the default lookback window unstated, gaps an agent would hit on first invocation.

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

Parameters3/5

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

Schema coverage is 100% and the single 'weeks' parameter already carries its default (8) and max (104) in the schema, so the description adds nothing about parameters. With one fully documented param, baseline 3 applies; it neither compensates nor is required to.

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 enumerates exactly what the tool reports (sessions, time, distance, avg HR, easy-zone share, effort, cardiac cost trend, volume by sport) per ISO week, so an agent knows the resource is a weekly training aggregate. It lacks an explicit verb ('returns/generates') and never distinguishes itself from near-neighbours like get_days or get_vitals, which is the only thing keeping it off a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of the scenario the tool serves (e.g. multi-week trend review vs. single-day inspection), no exclusions, and no alternatives named among get_day/get_days/get_vitals. Usage must be inferred purely from the metric list.

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