Skip to main content
Glama

rawwatts-demo

get_training_summary

Per week (Monday-Sunday) for the last weeks weeks (default 8, max 104): rides, hours, kJ and seconds per power zone (Coggan 1-7, by each ride's FTP).

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

Input Schema

NameRequiredDescriptionDefault
weeksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose non-obvious computation logic: weeks run Monday-Sunday, aggregation is per-week, and zones are Coggan 1-7 computed against each individual ride's FTP rather than a single athlete FTP. It remains silent on partial-current-week handling, timezone, and rides lacking FTP data, so it is informative but not fully disclosing.

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 dense sentence with the grouping key (per week) front-loaded, then the window, then the returned metrics. No filler and nothing redundant.

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 one-parameter read tool with no output schema, it covers the window, default, cap, grouping granularity, and returned metrics. The only notable gaps are partial-week behavior and timezone assumptions, which matter for a time-bucketed summary but are minor relative to what is given.

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% and the schema only shows a default of 8, so the description adds real meaning: `weeks` is a lookback window, defaults to 8, and is capped at 104. The max constraint and the lookback semantics exist nowhere in the schema.

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 specific resource and its shape: a per-week (Monday-Sunday) aggregation of rides, hours, kJ, and seconds per Coggan power zone. That output profile is distinctive enough to separate it from get_power_curve or list_rides, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no stated when-to-use or when-not-to-use guidance and no named alternative, e.g. list_rides for raw ride data or get_power_curve for distributions. The reader must infer the use case (periodized training overview) entirely from the output description.

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