Skip to main content
Glama

Series for a chart

get_cpet_series
Read-onlyIdempotent

A downsampled slice of the stored signals, for plotting the data or looking at a specific stretch of a recording. Not for analysis.

Every measurement Oxynet offers runs server-side on the full record at full resolution. This slice is decimated by stride, so a narrow feature can fall between two kept samples, and arithmetic on it is costlier and less accurate than the corresponding metric.

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

Input Schema

NameRequiredDescriptionDefault
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.
channelsNoChannel names, e.g. ["VE", "PetCO2"]. Defaults to ["VE"].
max_pointsNoSamples per channel, default 200. Each sample is about 3 tokens per channel, and a plot cannot resolve more points than it has pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / channels / description
      Added value: +"Channel names, e.g. [\"VE\", \"PetCO2\"]. Defaults to [\"VE\"]."
    • addedInput schema / properties / cpet_id / description
      Added value: +"Handle from upload_cpet, create_upload or get_sample_cpet."
    • addedInput schema / properties / max_points / description
      Added value: +"Samples per channel, default 200. Each sample is about 3 tokens per channel, and a plot cannot resolve more points than it has pixels."
  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 the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: the data is decimated by stride, features can fall between kept samples, and arithmetic on the slice is costlier and less accurate. That aliasing caveat is exactly the kind of failure mode an agent could not infer from the annotations or 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?

Two short paragraphs, zero filler. The identity and intended use come first, and the accuracy caveat follows as supporting rationale rather than burying the lede.

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 three-parameter read tool with full schema coverage, the description covers purpose, exclusions, and the key resolution caveat. The only gap is that it never sketches the return shape (e.g. per-channel sample arrays, whether a time axis is included), which matters somewhat since there is no output schema.

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%, with cpet_id provenance, channel examples, defaults, and even a token-cost note for max_points already documented in the schema. The description's mention of stride decimation obliquely informs max_points but adds no per-parameter meaning beyond the schema, so the baseline 3 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 says exactly what the tool returns — 'a downsampled slice of the stored signals' — and scopes it to plotting or inspecting a specific stretch of a recording. The clause 'Not for analysis' separates it from the analysis/metric siblings without the agent needing to open their 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?

It gives both the when ('plotting the data or looking at a specific stretch of a recording') and the when-not ('Not for analysis'), plus the reason: every measurement runs server-side at full resolution. That reason is what lets an agent choose compute_metrics/analyze_* over this tool for any quantitative question.

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