Skip to main content
Glama

List derived metrics

list_metrics
Read-onlyIdempotent

Every derived quantity Oxynet can compute, with what each one needs.

The registry covers peak values (VO2max, VEmax, RERmax, O2 pulse), the VE/VCO2 slope profile, substrate use and FATMAX, and input-quality checks (gas-channel agreement, sampling adequacy, clock integrity).

Each entry states its unit, the channels it requires, and the traps in reading it. It is the list of valid names for compute_metrics, and it grows without this tool changing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description's added value is the disclosure that the registry 'grows without this tool changing' — signalling the returned catalog is dynamic and not a fixed enum the agent can cache forever. It also describes entry contents (unit, required channels, reading traps), which matters because there is no output schema.

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?

Four short sentences, each earning its place: purpose, category coverage, entry structure, and the compute_metrics relationship plus volatility note. The scope statement is front-loaded and the parenthetical enumerations convey real information rather than filler.

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?

With no parameters and no output schema, the description carries the burden of explaining return contents, and it does: each entry's unit, required channels, and pitfalls. Combined with the volatility note and the link to compute_metrics, an agent has everything needed to call it and interpret the result.

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 beyond confirming the call is argument-free; baseline 4 applies.

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 opens with a specific verb-and-resource statement — 'Every derived quantity Oxynet can compute, with what each one needs' — then enumerates the categories (peak values, VE/VCO2 slope, substrate/FATMAX, input-quality checks) so the agent knows exactly what the registry contains. It also differentiates from the sibling compute_metrics by declaring itself 'the list of valid names for compute_metrics'.

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?

The sentence 'It is the list of valid names for compute_metrics' gives a clear use context: call this to discover valid metric names before computing. There are no explicit exclusions or 'do not use when' statements, and it does not say whether compute_metrics also returns the registry, but the routing signal is strong.

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