Skip to main content
Glama

rawwatts-demo

get_ride_series

A ride's second-by-second data averaged down to resolution_s (default 30; at most 720 points, so long rides get a coarser resolution). fields from: power, target, hr, cadence, right_pct, speed, distance, step. Default: power, hr, cadence. t_s is the start of each interval in recorded seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_ride_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fieldsNo
resolution_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key behavior: averaging/downsampling, a 720-point cap, default resolution, allowed fields, default fields, and t_s interval start. It does not cover permissions, error behavior, or response shape, but the core behavioral traits are present.

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?

The description is compact and front-loads the core operation. The field list and defaults are dense but necessary; there is little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and 0% schema coverage, the description covers the main return semantics and two parameters well. However, it omits the id parameter's meaning and does not describe the response structure beyond t_s, leaving some gaps for an agent invoking it.

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 coverage is 0%, so the description must compensate. It explains resolution_s default and cap, lists allowed fields and defaults, and defines t_s, but it never explains the required id parameter. That leaves one of three parameters undocumented.

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 the tool returns a ride's second-by-second data averaged to resolution_s, with selectable fields. It is specific about the resource and transformation, though it does not explicitly contrast with get_ride or other siblings.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description implies it is for downsampled time-series retrieval, but an agent must infer that from the output description rather than from stated alternatives.

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