Skip to main content
Glama

List workouts

list_workouts
Read-only

Completed workouts in a date range, newest first, with name, duration and session id (for get_workout).

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
daysNoHow many days back to look. Default 30.
limitNoMax workouts. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely useful behavior beyond that: results are ordered newest first and each row carries name, duration, and session id. It does not say whether results are truncated at limit or how the days window interacts with limit, which keeps it below 5.

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?

A single compact sentence that front-loads the resource and scope, then the ordering, then the returned fields. Every clause carries information an agent needs, with no filler or restatement of the title.

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 usefully enumerates the returned fields and their ordering, which is the main thing an agent would otherwise lack. The remaining gap is truncation/pagination semantics when limit is hit, but for a two-parameter read-only list tool this is close to complete.

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 description coverage is 100%, with both days and limit documented including their defaults and bounds, so the baseline is 3. The description reinforces the date-range notion but adds no syntax, edge-case, or interaction detail (e.g., precedence between days and limit) beyond what the schema already states.

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?

The description gives a specific verb and resource (completed workouts), the scoping filter (date range), the sort order (newest first), and the exact fields returned. It also explicitly distinguishes itself from get_workout by noting that the session id is provided for that tool, so an agent can tell the two apart without opening a 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?

Usage context is clear: this is the listing/entry point for completed workouts, and the parenthetical '(for get_workout)' signals the follow-up path to detail retrieval. There is no explicit when-not guidance or statement about behavior when the limit truncates results, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources