Skip to main content
Glama

list_workouts

Read-onlyIdempotent

Lists Apple Health and Apple Watch workouts as compact rows, newest first, with date, sport, distance, time, heart rate, and effort; filter by start date or sport.

Instructions

Compact rows, newest first, one line per session written for you: date, sport, distance, time, average heart rate, effort with its source and whether it is rated. Filter by start date and 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": "list_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows, default 20, max 200.
sinceNoOnly workouts starting on or after this date (`YYYY-MM-DD` or RFC 3339).
sportNoActivity filter: `pool_swim`, `indoor_row`, `cycle`, `walk`, `run` (`swim` matches both swim kinds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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), and the description adds real behavioral context beyond them: default sort order (newest first), row granularity (one line per session), and the exact set of returned attributes. It does not disclose the default/max row cap or what an empty result looks like, which keeps it from a 5.

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?

A single dense sentence front-loads the return shape, then the filters, with no filler. It is slightly run-on ('effort with its source and whether it is rated'), but every clause carries information.

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?

With no output schema, the description correctly carries the return-value burden by enumerating the row fields, and it states ordering and filtering. The remaining gap is pagination behavior and empty-result handling, both minor for a read-only list tool with full schema documentation.

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% – limit, since, and sport are all documented with formats and defaults in the schema. The description reiterates only the two filters ('start date and sport') and never mentions limit or its default of 20/max 200, so it adds little meaning over the structured fields.

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 names the resource (workout sessions) and precisely characterizes the output as 'compact rows, newest first, one line per session' with an explicit field list, which implicitly separates it from a detail-oriented sibling like get_workout. It never names that sibling or use a verb, so differentiation is by inference rather than statement.

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?

'Compact rows ... one line per session' implies an overview/listing use case, and 'Filter by start date and sport' states the supported narrowing. There is no explicit when-not guidance and no reference to get_workout for full detail, so an agent must infer the boundary itself.

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