Skip to main content
Glama

Summary of a recording

get_cpet
Read-onlyIdempotent

What is actually in an uploaded recording, without pulling the signals.

The signal-processing view of a file: the detected vendor format, which channels are present and how complete each one is, the sampling interval the FILE arrived at (before Oxynet resampled it), the external load and the protocol reconstructed from it, and every parser flag raised on the way in. The same summary upload_cpet returned, re-read on demand, so a conversation that has lost it needs no second upload. An unknown or expired handle returns CPET_NOT_FOUND, here and in every tool that takes one.

  • A channel with present: false carries a reason. Absent and present-but-reading-zero are different facts, and the reason says which.

  • load.available: false is an answer, not a gap. Most recordings carry no ergometer channel, and nothing is back-calculated from VO2 to invent one, so analyses that need watts report that they cannot run.

flags describes the RECORDING. It is not a confidence in any result.

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": {
      "cpet_id": "<cpet_id>"
    },
    "name": "get_cpet"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cpet_id / description
      Added value: +"Handle from upload_cpet, create_upload or get_sample_cpet."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world safety, and the description goes well beyond them: it discloses the error contract (unknown or expired handle returns CPET_NOT_FOUND, consistently across all handle-taking tools) and semantics an agent would otherwise misread — present:false carries a reason distinct from reading-zero, load.available:false is a real answer rather than missing data, and flags describe the recording rather than result confidence.

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?

Front-loaded with the one-line purpose, then supporting detail in bullets that each disambiguate a real misreading. Some prose is slightly verbose ('An unknown or expired handle returns CPET_NOT_FOUND, here and in every tool that takes one'), but no bullet is filler and the structure aids scanning.

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

Completeness5/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 carries the full burden of explaining return content — and it does: it enumerates the summary fields, the channel-present/reason convention, the load-availability convention, and the error case. Nothing an agent needs in order to call this correctly or interpret the result is missing.

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 100% and the single parameter is already documented as a handle from upload_cpet, create_upload or get_sample_cpet, so the baseline is 3. The description adds value on top by specifying what happens when the handle is unknown or expired (CPET_NOT_FOUND) and noting that this behavior is uniform across tools accepting a handle.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reading the summary of an uploaded recording, explicitly 'without pulling the signals', which implicitly separates it from the series/signal-fetching sibling. The bullet list further pins down exactly which fields constitute the summary (vendor format, channels, sampling interval, load, protocol, flags).

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

Usage Guidelines4/5

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

Explains the core use case well: it is the same summary upload_cpet returned, re-read on demand so a lost context needs no re-upload. It also signals the boundary against signal-pulling tools via 'without pulling the signals'. It stops short of explicitly naming get_cpet_series as the alternative when signal data is actually needed.

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