Skip to main content
Glama

waveform

Retrieve up to 200 raw signal samples by offset, including timestamps, from a run ID or portable record path for review and comparison.

Instructions

Get 1..200 raw samples by offset, including timestamps. Also accepts a portable record path.

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": {
      "run_id": "<run_id>"
    },
    "name": "waveform"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral disclosure burden. It does reveal that this is a read-style retrieval operation with a 1..200 sample cap, offset-based paging, timestamps in the result, and support for a portable record path. It omits authentication needs, error behavior, rate limits, and detailed return structure.

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?

The description is two short sentences and front-loads the core operation. There is no filler, though the second sentence about a portable record path is ambiguous and would benefit from clearer parameter mapping.

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?

For a three-parameter retrieval tool with no annotations and no output schema, the description covers the core operation, sample cap, offset paging, and timestamps. It still leaves gaps around the required run_id parameter, count/start defaults, and the exact return format, so it is minimum viable rather than complete.

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 0%, so the description needs to compensate. It adds meaning for the count bound (1..200), the offset concept, and suggests that a portable record path may be accepted, but it does not explicitly map the path to run_id, explain that run_id is required, or clarify the count and start defaults.

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 states a specific verb and resource: get raw samples by offset, including timestamps. It also gives a clear scope of 1..200 samples and mentions an alternate portable record path. It does not explicitly differentiate this from sibling retrieval tools such as get_run or read_parameters, so it falls short of a 5.

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, no when-not-to-use guidance, and no named alternatives. The retrieval intent is implied by 'Get raw samples', but an agent is left to infer when this tool should be selected over sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.