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

mcp-server-siglent-sdm3045x

by shaag7967

sample

Idempotent

Record timestamped multimeter readings at a fixed interval and return statistics plus all readings for time-based measurement capture.

Instructions

Record timestamped readings at a fixed interval and return statistics plus all samples.

Readings are paced by this computer. A reading takes about 0.3 s at speed slow and in most other functions, 0.6 s for frequency and period; with a shorter interval readings are taken back to back, and none starts later than one interval after duration_s, so the recording ends on time with fewer samples. Without function the present function and range are kept; otherwise they are set as in measure.

Args: duration_s: Recording time in seconds (max 600). interval_s: Time between readings in seconds (min 0.1). 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNo
speedNo
sensorNo
functionNo
duration_sNo
interval_sNo

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?

Beyond the annotations, the description discloses detailed behavior: reading duration depends on speed/function, shorter intervals cause back-to-back readings, no reading starts later than one interval after duration_s, and the recording ends on time with fewer samples. It also explains state persistence when function/range are omitted. These are meaningful operational details not available from the annotations.

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 and the Args section is structured, with detail warranted by zero schema coverage. The pacing sentence is somewhat dense and could be clearer, but there is little wasted content.

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?

An output schema exists, so return values need not be explained. The description covers timing behavior, parameter constraints, state persistence, and function-specific applicability for a complex six-parameter tool. Nothing material appears missing.

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 parameter burden. It documents all six parameters: duration max, interval min, function lead selection, valid range values per function, speed applicability, and sensor requirements for temperature. This adds essential meaning beyond the bare schema.

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 clearly states a specific action: recording timestamped readings at a fixed interval and returning statistics plus all samples. The scope and output are clear. It references measure for inherited settings, but does not explicitly position itself against burst or read, so sibling differentiation is incomplete.

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?

The description implies this tool is for timed recording rather than a single measurement, and says omitted function/range keep the present settings while otherwise they are set as in measure. However, it gives no explicit when-to-use versus alternatives like measure, burst, or read, and no exclusions.

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