Skip to main content
Glama

PVQA: impairment timeline

pvqa_timeline
Read-only

Impairment timeline of an uploaded WAV file: which impairments PVQA detects at which time.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "pvqa_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNochannel to analyze, from 0 (default 0)
upload_idYesupload_id of a WAV file
resolution_msNotime step of the returned rows in ms (default 250, min 10); each row holds the maximum of every numeric column in its window. Coarsened automatically to stay within 1000 rows

Output Schema

NameRequiredDescriptionDefault
rowsYes
channelYes
columnsYesTime (seconds, window start), then detector values
upload_idYes
resolution_msYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that results are framed as impairment detections over time; it says nothing about the automatic coarsening to 1000 rows, the idempotentHint=false implication, or how detection gaps appear in the timeline, leaving the notable behaviors to the schema.

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?

A single front-loaded sentence with zero filler that states both the input object and the nature of the output. It is efficient, though its brevity leaves room it could have used for sibling differentiation at almost no cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and annotations cover safety. What remains missing is the upload prerequisite and any hint about the resolution/row-cap tradeoff that materially affects results for a three-parameter analysis tool.

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 channel, upload_id, and resolution_ms (including the default 250, min 10, and per-window max aggregation) are already fully documented. The description adds no further meaning to any parameter, which is the expected baseline when the schema does the work.

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 a specific resource (an uploaded WAV file) and a specific return shape: which impairments are detected at which times. That is clear enough to distinguish a temporal view from a general analysis, though it never explicitly contrasts itself with the sibling pvqa_analyze or pvqa_detector.

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 statement of when to choose a timeline over pvqa_analyze or pvqa_detector, nor any prerequisite guidance such as needing an upload_id from create_upload first. The only implied usage is that it is the time-resolved view; nothing tells the agent when that matters.

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