Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
self_configA

Discover/connect an instrument and attach it to the session.

Call this first — every other tool needs a connected instrument. Runs the
transport cascade (USB → LAN → manual host); pass ``host`` to skip discovery
and target a known address.
identifyA

Return the connected instrument's identity (vendor, model, serial, firmware).

Takes no arguments; requires a prior self_config.
capability_reportA

Report the connected instrument's detected capabilities.

Returns channel count/ids, bandwidth, source & logic support, max memory
depth, and installed options. Takes no arguments; requires a prior
self_config. Use it to learn what the scope can do before driving it.
capture_screenA

Capture the on-screen waveform for one channel (~1200 points).

capture_memoryB

Capture the deep-memory waveform for one channel (full sample-rate record).

capture_alignedA

Capture multiple channels on the same time base, time-aligned.

The instrument shares one time base across channels, so a sequence of reads is already time-aligned. (Real hardware reads them back-to-back; the mock is instantaneous.) Use this to compare two signals sample-for-sample.

measureA

Take a single measurement of one quantity on one channel.

measure_snapshotC

Take several measurements at once on one channel (one read per quantity).

measure_seriesA

Poll one measurement repeatedly, returning a short time series.

Useful for watching a value drift or settle (e.g. a ramping duty cycle).
``interval_s`` is honored via the instrument's settle hook so the mock stays
instant in tests while real hardware actually waits between reads.
set_channelA

Set a channel's vertical configuration (enable, V/div, offset, coupling).

Only the arguments you pass are changed; omit any to leave it as-is. Use this to fit a signal on screen before measuring or capturing.

set_timebaseA

Set the horizontal time base (seconds/div and trigger offset).

Controls how many periods of the signal are shown; widen s/div to see slow events, narrow it to resolve fast ones. Shared across all channels.

set_triggerA

Configure the edge trigger (source channel, level, slope).

Sets up a stable trigger so repetitive signals hold still, or so a
single-shot (see acq_single) fires on the right edge of a one-off event.
acq_runA

Start continuous (free-running) acquisition. Disruptive — needs confirm=True.

acq_stopA

Stop acquisition, freezing the current trace. Disruptive — needs confirm=True.

acq_singleA

Arm a single-shot acquisition: capture one trigger then stop. Needs confirm=True.

Pair with set_trigger to catch a one-off transient (e.g. a power-on spike).
acq_forceA

Force a trigger now, ignoring the trigger condition. Needs confirm=True.

acq_configureA

Set acquisition type and/or memory depth. Disruptive — needs confirm=True.

Deeper memory captures more points at a given time base; averaging/peak modes trade update rate for noise rejection or glitch capture.

characterize_signalA

Characterize the signal on channel — the FLAGSHIP goal-level tool.

Runs the probe → vertical fit → horizontal fit → trigger hunt → characterize
loop, settling and re-verifying after each adjustment (bounded by
:data:`MAX_SETTLE_ITERATIONS`). Returns the discovered signal parameters, a
full measurement snapshot, and a confidence flag. When ``export_path`` is
given, the deep-memory capture is rendered to a PNG there.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/armchairdeity/mcp-server-scpi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server