Skip to main content
Glama

mywhoosh_list_workouts

Retrieve custom cycling workouts from MyWhoosh, newest first, with optional name filtering and per-step breakdowns to review or choose a session.

Instructions

List custom cycling workouts stored in MyWhoosh (newest first).

include_steps adds a compact per-step breakdown. name_contains filters case-insensitively.

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

Input Schema

NameRequiredDescriptionDefault
include_stepsNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add real behavior: result ordering is newest-first, include_steps produces a 'compact per-step breakdown' (signalling it is a summary, not a raw dump), and name filtering is case-insensitive. It does not say whether the call is read-only (only implied by 'List'), whether results are paginated or capped, or which fields each workout returns.

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 short sentences, zero filler, with the resource and ordering front-loaded and parameter notes following. Every clause carries distinct 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?

For a two-optional-parameter read tool with no output schema, the description covers purpose, ordering, and both parameters adequately. The remaining gap — pagination/result limits and the shape of returned workout objects — is minor but not trivial for a listing tool.

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 0% — the schema only supplies titles like 'Include Steps' — so the description must compensate, and it does: include_steps is defined as a compact per-step breakdown and name_contains as a case-insensitive match. It stops short of match semantics (substring vs prefix) and the default behavior when name_contains is null.

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?

States a specific verb and resource — 'List custom cycling workouts stored in MyWhoosh' — plus the default ordering ('newest first'). It does not explicitly distinguish itself from mywhoosh_list_scheduled_workouts, but 'custom cycling workouts' is specific enough that an agent can tell it is the library listing rather than a schedule listing.

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?

Usage is implied rather than stated: include_steps implies a cheap default listing with optional detail, and name_contains implies text search. There is no explicit 'use this when…' or a named alternative for scheduled workouts, so the agent must infer the boundary from sibling names alone.

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