Skip to main content
Glama

rawwatts-demo

get_ride

One ride's full summary as the app computed it: stats (incl. normalized power), laps, power curve, power zones, left/right balance, heart rate, DFA-alpha1 per minute (experimental), the workout ridden and the FTP used.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: values are precomputed "as the app computed it," the specific FTP used is surfaced, and DFA-alpha1 is flagged experimental — real context about data provenance and trustworthiness. It says nothing about permissions/ownership requirements, behavior for an invalid id, or payload size for a full summary, which leaves a meaningful gap for a no-annotation, no-output-schema tool.

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?

One dense sentence that front-loads the core purpose (one ride's full summary) then qualifies what is included. Every listed item earns its place by signaling payload scope; 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?

For a 1-parameter read tool with no annotations and no output schema, the description does the essential work of specifying what comes back, down to sub-fields like per-minute DFA-alpha1 and the FTP basis. Missing pieces — id provenance/format and failure behavior — are minor relative to the strong return-content coverage.

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% and the single parameter "id" has no description, so the description bears responsibility; "One ride's full summary" does imply the id selects one specific ride (rather than a date range or athlete). It gives no format, type, or sourcing hint (e.g., where to obtain the id from list_rides), so the compensation is only partial.

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 resource precisely ("One ride's full summary") and enumerates its contents — stats with normalized power, laps, power curve, power zones, L/R balance, HR, DFA-alpha1, workout, FTP — which separates it from siblings like get_ride_series or list_rides by scope of payload. It lacks an explicit verb and never names a sibling to contrast with, so it falls short of the 5 bar.

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 when-to-use guidance: no statement of when to call this vs. get_ride_series, list_rides, or get_power_curve, and no prerequisites such as needing a valid ride id or ownership of the ride. The enumerated content list implies a 'full detail fetch' but the agent must infer that selection logic itself.

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