Skip to main content
Glama

Analyse fat and carbohydrate use

analyze_substrate

Analyses fat and carbohydrate oxidation from gas exchange in an uploaded recording: FATMAX, peak fat oxidation, the crossover to carbohydrate and gross efficiency, with stage means and fitted curves. For the headline FATMAX numbers alone, compute_metrics with ["substrate_summary"] costs about a sixth of the tokens.

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

Input Schema

NameRequiredDescriptionDefault
curvesNoAlso return the sampled curve points, for plotting. Off by default: the points are the fitted cubic evaluated on a grid and double the envelope. Measured values are unaffected.
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 / curves / description
      Added value: +"Also return the sampled curve points, for plotting. Off by default: the points are the fitted cubic evaluated on a grid and double the envelope. Measured values are unaffected."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With annotations supplied, the description adds real substance beyond them: billing is one unit of the key's monthly allowance, repeated calls count again, licensing is separate, and quality describes the INPUT rather than the answer. It also discloses output shape (status ok/not_analysable, confidence as a reason list never a number), which annotations cannot convey. The main residual gap is that idempotentHint=false and readOnlyHint=false are not explained — the tool is non-mutating in spirit yet non-idempotent, and the description never says what a re-run costs or whether results are cached.

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 capability statement, then the cost alternative, then a structured enumeration of the return envelope. The dense field listing is long but each clause carries distinct information; a minor cost is that the return-field sentence packs many concepts into one unbroken run.

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 must describe results itself, and it does so thoroughly: envelope key, status values, findings, quality, confidence semantics, notes, provenance, and error/message. Combined with the billing and licensing notes, an agent has everything needed to call it and interpret the answer.

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?

Schema description coverage is 100%, so both parameters are already documented in the input schema, and the curves token-doubling rationale appears there rather than in the description. The description only alludes to the input as "an uploaded recording" and adds no format, grid or sampling detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (analyses fat and carbohydrate oxidation from gas exchange) and enumerates the derived outputs: FATMAX, peak fat oxidation, crossover, gross efficiency, stage means and fitted curves. It also differentiates itself from the sibling tool compute_metrics for the headline-numbers-only case, so an agent can pick between them without opening a schema.

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 an explicit alternative route: "For the headline FATMAX numbers alone, compute_metrics with [\"substrate_summary\"] costs about a sixth of the tokens", which tells the agent both when to use the sibling and the cost trade-off behind that choice. It also flags the separate licensing prerequisite and points to get_capabilities to check entitlement.

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