Skip to main content
Glama

rawwatts-demo

list_rides

The rider's rides, newest first: id, local start, duration, kJ, average and max power, average and max heart rate, kind (free, ramp, rampLite, edge, workout). Dates are YYYY-MM-DD in the rider's local time, both inclusive. limit: 1-500, default 50. Ids follow the order the app synced the rides, not the ride dates.

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_rides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
to_dateNo
from_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses sort order ('newest first'), that both date bounds are inclusive in the rider's local time, the acceptable limit range and default, and the non-obvious caveat that ids follow sync order rather than ride dates. What is missing is pagination behavior beyond the limit cap and any auth/scope requirement.

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?

Dense and front-loaded: returned fields first, then date semantics, then limit, then the id-ordering caveat. Every clause conveys operational information and there is no filler.

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, listing the returned columns is exactly the right compensation, and the ordering caveat prevents a likely agent mistake. Only minor gaps remain, such as whether omitting both dates returns the full history and whether the 500 limit implies manual paging.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate and it does: limit is given bounds (1-500) and a default (50), and from/to dates are given an explicit format (YYYY-MM-DD), timezone semantics (rider's local time), and inclusivity. All three parameters are covered with meaning the bare schema lacks.

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 resource ('the rider's rides') and enumerates exactly what each row contains (id, start, duration, kJ, power/HR averages and maxes, kind), so an agent can tell this is a bulk list rather than a single-ride fetch. It stops short of naming sibling tools like get_ride or list_workouts, so differentiation is inferred rather than stated.

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 spelled out: the date filters and limit bounds suggest paging through a rider's history, and the 'newest first' ordering hints at recency queries. There is no explicit when-to-use versus get_ride or get_ride_series, and no mention of prerequisites such as athlete identification.

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