Skip to main content
Glama

rawwatts-demo

get_athlete

The rider's body settings (FTP, FTP history, max HR, weight, age in years, units), the dates of their first and last ride, the ride count and when the app last synced. ftp_history only holds FTPs a test replaced ("Use as FTP"); an FTP the rider typed in is not recorded there.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, the description carries the full burden; it does disclose what data is returned and adds a genuinely useful caveat that ftp_history only contains test-replaced FTPs and omits manually entered ones. However, it never states that this is the authenticated rider's own record, whether the call is read-only, or what happens on auth failure, so meaningful behavioral gaps remain.

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?

Two sentences with no filler, and the FTP caveat is placed after the field inventory where it belongs. The opening is a bare noun phrase rather than a verb-led statement of intent, which is a minor structural weakness.

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?

There is no output schema, so the description must describe the return payload, and it does so broadly (settings, ride boundaries, ride count, sync timestamp) including the non-obvious ftp_history semantics. It is nearly complete for a zero-argument read tool, lacking only ownership/auth framing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its budget on return-value semantics, which is appropriate here.

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 enumerates a specific resource's contents (FTP, FTP history, max HR, weight, age, units, first/last ride dates, ride count, last sync), which makes the retrieval intent unambiguous even though the verb 'get' only appears in the tool name. It is distinguishable from siblings like get_power_curve or get_training_summary by content, but it never explicitly frames itself as a read of the athlete profile.

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 statement about when to call this versus alternatives such as get_training_summary or get_power_curve, and no prerequisite or context noted. An agent must infer usage purely from the field list.

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