Skip to main content
Glama

Assess a recording

assess_cpet

One call on an uploaded recording: the kind of test, VT1 and VT2 from the best-suited method, oscillatory ventilation (beta: one heart-failure cohort, transportability untested) and substrate use when the channels allow, and the derived metrics. Runs only what the key includes; plan says why a part did not. confidence per result, repeated in headline. One unit per analysis run, a repeated call included.

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

Input Schema

NameRequiredDescriptionDefault
cpet_idYesHandle from upload_cpet, create_upload or get_sample_cpet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare the safety profile, and the description adds real behavior: partial execution with `plan` explaining omissions, per-result `confidence` repeated in `headline`, metering ('one unit per analysis run, a repeated call included') which confirms cost is incurred again on retry, and an explicit scientific caveat that the oscillatory-ventilation beta rests on a single heart-failure cohort with untested transportability. What is missing is any statement of failure modes, latency, or required input quality.

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?

Very compact and front-loaded on the action, with no filler sentences. The cost is density: fragments like 'the kind of test, VT1 and VT2 from the best-suited method' and 'One unit per analysis run, a repeated call included' take effort to parse and the latter's meaning is ambiguous.

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 output schema, the description takes on the job of describing the return shape and does: analysis outputs, `plan` for skipped parts, and `confidence`/`headline`. Combined with annotations covering safety and a fully documented single parameter, an agent has what it needs to call this correctly.

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?

There is a single required parameter at 100% schema coverage, and its description already states it is a handle from upload_cpet, create_upload, or get_sample_cpet. The description adds nothing further about it, so the schema carries the full burden and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (an uploaded recording) and enumerates exactly what the call produces: test kind, VT1/VT2 from the best-suited method, oscillatory ventilation, substrate use, and derived metrics. That makes it distinguishable from single-purpose siblings like analyze_vt or analyze_substrate, though it never says outright that it is the aggregate of them.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. 'Runs only what the key includes' tells the agent the call may do less than advertised, but nothing says when to prefer this composite over the individual analyze_* or compute_metrics tools, which is the main routing decision an agent faces here.

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