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

mcp-server-siglent-sdm3045x

by shaag7967

read

Idempotent

Takes a single measurement from a Siglent SDM3045X multimeter using current function, range, and speed settings, returning value, unit, range, timestamp, and accuracy.

Instructions

Take one reading with the function, range and speed currently set on the instrument.

Function, range and speed are kept; the trigger is set to immediate with one reading per trigger, as measure does. Returns value, unit, range, timestamp (UTC) and, where the data sheet allows, the accuracy.

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": "read"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: it discloses that the instrument's function/range/speed are preserved, that the trigger is reconfigured to immediate with one reading per trigger, and what comes back. This explains why readOnlyHint is false for an operation otherwise named 'read' — a real ambiguity resolved. It stops short of stating timing/blocking behavior or what happens on instrument error.

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?

Three short sentences, front-loaded with the core action, then state effects, then return value. The 'as measure does' comparison is the one clause that adds ambiguity rather than information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description needn't enumerate returns, though it does briefly. For a zero-parameter instrument action, the key facts — what state is used, what state changes, what comes back — are all present.

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

Parameters4/5

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

Zero parameters, so the schema carries no burden. The description usefully clarifies that the call implicitly uses whatever function, range and speed are currently configured rather than requiring arguments.

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 names a concrete action and resource ('take one reading') and the instrument state it acts on (function, range, speed currently set). It does not clearly separate itself from the sibling 'measure' — in fact 'as measure does' implies the two behave alike, which could make an agent unsure which to pick.

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?

No explicit guidance on when to use 'read' versus 'measure', 'sample' or 'burst'. The only comparative statement ('as measure does') describes trigger behavior rather than a selection criterion, so the agent has to guess.

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