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

mcp-server-siglent-sdm3045x

by shaag7967

burst

Idempotent

Capture rapid measurement bursts from a Siglent SDM3045X multimeter, returning all readings and statistics for fast data acquisition.

Instructions

Take a series of readings as fast as the instrument can and return statistics plus all values.

Readings are paced by the instrument and have no individual timestamps. Approximate rates (50 Hz mains): dc_voltage, dc_current and resistance 4/s at speed slow, 40/s medium, 175/s fast; ac functions and temperature 4/s; frequency and period 2/s. Bursts estimated to take longer than 600 s are refused. Without function the present function and range are kept; otherwise they are set as in measure.

Args: count: Number of readings, 1 to 10000. 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": "burst"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
rangeNo
speedNo
sensorNo
functionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations: no per-reading timestamps, instrument-paced timing, approximate rates by function and speed, duration refusal, and how function/range are retained or changed. These details let an agent predict latency and side effects; annotations already cover safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and return, then uses a structured Args section; the length is justified by five undocumented parameters and instrument-specific constraints. Almost every sentence adds operational detail.

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?

Complete for a complex instrument operation: the output schema handles return structure, while the description covers timing, duration limits, configuration persistence, and parameter requirements. The only minor omission is explicit sibling routing.

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%, and the description fully compensates: count range, function enum with lead requirements, valid ranges per function, speed restrictions and sensor requirement. This is substantially more than the raw schema provides.

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 action and return payload: take a series of readings at the instrument's maximum rate and return statistics plus all values. It references measure only for function/range configuration, not to explain when burst should be chosen over measure or sample, so sibling differentiation is partial.

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

Usage Guidelines4/5

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

Gives clear context for use: many readings in one fast burst, with explicit refusal above 600 s and defaults for function/range. It does not state when to use measure, sample or read instead, nor any exclusion beyond the duration limit.

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