Skip to main content
Glama

Load the synthetic sample

get_sample_cpet

Load Oxynet's synthetic CPET (not a real person) and get a cpet_id back, ready to analyse: for demonstrating Oxynet or testing a connection without a patient file. Real CPET exports are health data, and their filenames often carry patient names.

Returns the same summary upload_cpet returns. The recording is analysed like any other and deleted after 24 h, or at once with delete_cpet.

The thresholds in the plain sample sit near 55 % and 80 % of the exercise period because they were placed there. It is a demonstration fixture, not validation data and not evidence of accuracy.

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

Input Schema

NameRequiredDescriptionDefault
oscillatingNoTrue for a recording that exercises the oscillatory ventilation detector. False for a plain incremental test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / oscillating / description
      Added value: +"True for a recording that exercises the oscillatory ventilation detector. False for a plain incremental test."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and the other hints; the description adds the meaningful lifecycle: a recording is created, analysed like any other, and auto-deleted after 24 h or immediately via delete_cpet. It also flags that the 55%/80% thresholds were placed deliberately and are not validation evidence, which prevents a real misreading of results.

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?

Purpose and return value are front-loaded in the first sentence, with lifecycle and caveat paragraphs following in a logical order. The phrasing is slightly verbose in places but no sentence is 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 fixture-loading tool with a side effect and no output schema, the description covers creation, retention, deletion, and return shape adequately. The return value is defined only by reference ('the same summary upload_cpet returns'), which requires knowing the sibling, a small remaining gap.

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?

The only parameter, oscillating, is fully documented in the schema (100% coverage, including the detector intent), so the schema carries the semantic load. The description adds no further parameter guidance such as when to prefer the oscillating fixture. Baseline 3 is appropriate.

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?

The description names a specific verb and resource ('Load Oxynet's synthetic CPET') and states the concrete outcome ('get a cpet_id back'), immediately distinguishing it from a real-data load by parenthetically saying 'not a real person'. An agent can tell this apart from upload_cpet without opening either schema.

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?

It gives clear when-to-use guidance ('for demonstrating Oxynet or testing a connection without a patient file') and implicitly when-not by noting real CPET exports are health data with names in filenames. It does not explicitly say 'use upload_cpet for real files', leaving the alternative to inference, which keeps it short of a 5.

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