Skip to main content
Glama

rawwatts-demo

get_power_curve

Best average power per duration (5 s to 60 min) over a period, with the ride each best came from. Dates YYYY-MM-DD, inclusive; both optional (default: all rides).

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

Input Schema

NameRequiredDescriptionDefault
to_dateNo
from_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the shape of the result (best power per duration plus originating ride) and the default scope, but says nothing about required auth, cost of computation over a long history, units (watts), or how durations are sampled/gridded.

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 compact semicolon-delimited sentence, front-loaded with what the tool returns before the date mechanics. Nothing is 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?

With two optional params, no annotations and no output schema, the definition covers the essentials: output composition, duration range, date semantics, and defaults. Minor gaps remain (units, and whether an empty period yields an empty set), but an agent can call it correctly as written.

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%, so the description must compensate, and it largely does: it specifies the YYYY-MM-DD format, that the range is inclusive, that both bounds are optional, and that omitting them means all rides. It does not explicitly map from_date vs to_date, but that pairing is unambiguous.

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 a specific resource (best average power per duration, 5 s to 60 min) and the scope of the period, and it states that each entry carries the source ride. That is enough to tell it apart from siblings like get_ride_series or get_training_summary, 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 Guidelines3/5

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

It gives useful framing—both dates optional, defaulting to all rides—which tells an agent the tool works fine with no arguments. It does not say when to prefer this over get_ride_series or get_training_summary, nor name any exclusion, so usage is only implied.

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