Skip to main content
Glama

measure

Read-only

Read a selected built-in oscilloscope reading from channel 1 or 2, including frequency, RMS, rise time, and duty cycle; returns null with valid=false when no valid signal is present.

Instructions

Read a built-in measurement. Invalid/no-signal readings return null with valid=false.

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": {
      "channel": "<channel>",
      "measurement": "<measurement>"
    },
    "name": "measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
measurementYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/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 does add genuinely useful behavior beyond that: invalid or no-signal conditions return null with valid=false, telling the agent how failure manifests instead of an error. It still says nothing about when a reading is considered stale or whether the instrument must be triggered/acquiring first.

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?

Two short sentences, front-loaded with the core action and followed by the failure-mode note; no filler or repetition. It is appropriately sized for the amount of information conveyed, though it is arguably too terse given the undocumented parameters.

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?

An output schema exists, so return values need not be explained, and the readOnly annotations cover side effects. However, with 0% schema description coverage on two required enum parameters, the definition leaves the agent guessing about channel selection semantics and measurement preconditions, which is a real gap for an otherwise simple read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for both parameters, but it mentions neither 'channel' nor 'measurement'. The enums list values (1/2, frequency…positive_duty_cycle) without conveying meaning such as whether channel 1 is the default source or that rise_time/fall_time require an edge, so no compensation for the coverage gap is provided.

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?

States a specific verb ('Read') and resource ('a built-in measurement'), which is clearer than a tautology like 'measure signal'. It does not explicitly differentiate itself from lookalike siblings such as advanced_read or inspect_signal, so an agent must infer that this returns instrument-computed scalar values rather than raw samples.

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 when-to-use guidance: nothing says to prefer this over waveform/acquisition for scalar measurements, nor any prerequisite about the channel being active or the acquisition running. Usage is only implied by the verb 'Read'.

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