Skip to main content
Glama

Find ventilatory thresholds

analyze_vt

Finds VT1 and VT2 in an uploaded recording with Oxynet's models trained on expert-labelled tests: the time of each and the VO2 at it. Unnamed, the model best suited to the recording answers, named with the reason in provenance.selection. Everything at once is assess_cpet; a single number is compute_metrics.

Returns cpet_id and one envelope in results: status ("ok" or "not_analysable"), findings, quality (good/acceptable/poor, of the INPUT, not of the answer), confidence ("low" or "normal" with the reasons, never a number), notes, provenance, and error/message when it could not run. Counts one unit of the key's monthly allowance, a repeated call included. Licensed separately (get_capabilities lists this key's analyses).

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

Input Schema

NameRequiredDescriptionDefault
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.
model_nameNoThreshold model. Unset, the best available method for this recording is chosen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / model_name / description
      Previous value: -"Threshold model. Unset, the server's default applies, the same one the web application shows."New value: +"Threshold model. Unset, the best available method for this recording is chosen."
  2. Changed2 schema fields changed
    • addedInput schema / properties / cpet_id / description
      Added value: +"Handle from upload_cpet, create_upload or get_sample_cpet."
    • addedInput schema / properties / model_name / description
      Added value: +"Threshold model. Unset, the server's default applies, the same one the web application shows."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations: it discloses that each call consumes one unit of the key's monthly allowance including repeats, that the capability is licensed separately (checkable via get_capabilities), that confidence is qualitative never numeric, and that quality grades the INPUT not the answer. It does not explain what happens when status is 'not_analysable' or whether a failed run still bills, leaving a small billing-failure ambiguity.

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?

Purpose and sibling disambiguation come first, then the return envelope, then cost/licensing. Sentences are dense but each carries distinct information; nothing is repeated from the title or schema.

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 no output schema, the description compensates by enumerating the result envelope fields and their semantics, which is exactly what an agent needs. Minor gap: no statement about latency, whether a returned 'not_analysable' still consumes quota, or how 'low' confidence should alter downstream reasoning.

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%, so the baseline is 3, but the description adds real meaning to model_name by explaining the default selection behavior and where the choice is reported. cpet_id handling is left entirely to the schema, which already names its source tools.

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 (finds VT1 and VT2 in an uploaded recording) and the concrete outputs (time of each and the VO2 at it). It also explicitly separates this from assess_cpet ('everything at once') and compute_metrics ('a single number'), so an agent can route without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit sibling routing rules with the selecting condition: whole-picture analysis goes to assess_cpet, a single value goes to compute_metrics. It also covers the model_name decision rule (unnamed = best-suited model is chosen, with its reason surfaced in provenance.selection).

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