Skip to main content
Glama
mcp-server-siglent-sdm3045x

mcp-server-siglent-sdm3045x

by shaag7967

measure

Idempotent

Select a multimeter function and take one reading, using autorange or a fixed range; returns value, unit, range, UTC timestamp and accuracy where available.

Instructions

Select a measurement function and take one reading.

This switches the instrument (front panel included) to the given function, with autorange unless a range is given. Returns value, unit, range used, timestamp (UTC) and, where the data sheet allows, the accuracy of the reading.

Args: function: Measurement function. Leads in HI/LO for voltage, resistance_2w, capacitance, frequency, period, continuity, diode and temperature; in I/LO for currents; resistance_4w also uses HI Sense/LO Sense. range: Fixed range in V, A, Ω or F; omit for autorange. dc_voltage 0.6, 6, 60, 600, 1000; ac_voltage 0.6, 6, 60, 600, 750; dc_current 0.0006, 0.006, 0.06, 0.6, 6, 10; ac_current 0.06, 0.6, 6, 10; resistance_2w/resistance_4w 600, 6000, 60000, 600000, 6e6, 6e7, 1e8; capacitance 2e-9, 2e-8, 2e-7, 2e-6, 2e-5, 0.0002, 0.01. Other functions have no range. speed: Only for dc_voltage, dc_current, resistance_2w, resistance_4w: slow (10 PLC, default, most accurate), medium (1 PLC), fast (0.3 PLC). sensor: Required for temperature: pt100 (RTD) or thermocouple type B, E, J, K, N, R, S or T.

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

Input Schema

NameRequiredDescriptionDefault
rangeNo
speedNo
sensorNo
functionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Without relying on the annotations, the description discloses that the call changes instrument state including the front panel (explaining the readOnlyHint=false despite a measurement), that autorange is the default, that `speed` trades PLC count against accuracy, and what the reading includes. That is materially more than the annotation block conveys.

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 purpose is front-loaded in one sentence and the Args block is dense reference material rather than padding. The long per-function range list is heavy, but with 0% schema coverage that detail has to live somewhere, so it earns its place.

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?

For a four-parameter tool with enum-constrained inputs and conditional requirements, every branch is covered: autorange vs fixed range, speed applicability, temperature sensor, and the state change it causes. An output schema exists, and the reading-summary sentence is a small bonus rather than a gap.

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

Parameters5/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 full burden and does: it maps each function enum value to its wiring (HI/LO vs I/LO, HI Sense/LO Sense), enumerates valid ranges per function with units, restricts `speed` to four functions with accuracy implications, and states that `sensor` is required for temperature with valid types.

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 first sentence gives a specific verb+resource pair: select a measurement function and take one reading, plus the side effect that it switches the instrument (front panel included). It implicitly distinguishes itself from `burst`/`sample` by saying 'one reading', but it never names those siblings or states the contrast explicitly, so the agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: pick a function, omit `range` for autorange, add `sensor` for temperature. Nothing tells the agent when to call `measure` versus `sample`, `read`, or `burst`, which is exactly the decision it faces among these siblings.

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

Deploy Server

Other Tools