Skip to main content
Glama

rawwatts-demo

list_workouts

Every workout set as text: the rider's own (read-only for you) and each assistant's, with who wrote it. The workout format is in save_workout's description.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden and largely does: it discloses that access is read-only for the caller, that results include other assistants' workouts as well as the rider's, that authorship is returned, and that output is text rather than structured data. It omits pagination, ordering, and result-size behavior, 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?

Two short sentences, front-loaded with what is returned and what is included. The cross-reference to save_workout for the format avoids duplicating a long format spec, though it does require a second lookup.

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 zero-parameter, schema-free list tool with no annotations and no output schema, the description covers the essentials: read-only nature, included entities, authorship, and output shape, with the format spec delegated. Missing detail on ordering or result limits is a minor gap given the tool's simplicity.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add. The baseline of 4 applies; the note about the workout format being defined in save_workout's description is a useful contract pointer rather than parameter documentation.

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 concrete resource (every workout set) and output form (as text), plus scope: the rider's own plus each assistant's, with authorship. That is more than the name alone conveys. It does not differentiate against sibling list tools such as list_rides, which is the remaining gap.

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 by 'every workout set as text' and the note 'read-only for you', which tells the agent this is a safe viewing operation. There is no explicit when-to-use vs alternative, no exclusion, and no prerequisite stated; the agent has to infer the trigger from the name.

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