Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOOPTRIAL_HOMENoThe LoopTrial experiment/lab directory used by the CLI and MCP server. From GUI-launched clients, specify the same LOOPTRIAL_HOME in the configuration.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use existing conversation conditions and discover the selected device. Read effective parameters. A diagnosis may require only one capture. Before tuning, record a baseline and select bounded goals, constraints, repeat conditions and a budget. Apply only declared temporary parameters. Inspect each response and verify any restoration. Confirm a passing candidate in fresh runs with new IDs.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

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

Tools

Functions exposed to the LLM to take actions

NameDescription
devicesA

List simulated devices, serial candidates and the BLE preset. Use describe to handshake.

describeC

Discover firmware identity, signal units, parameters, permitted actions, conditions and metrics.

read_parametersC

Read back the device's current effective values.

apply_parametersC

Apply bounded temporary values and read back. Returns previous, applied and independently verified values.

parameter_historyC

Retrieve write and recovery receipts, newest first.

run_experimentA

Acquire one declared action, with optional metric bounds {name: {le: max, ge: min}}. Returns ID, conditions, effective config, metrics, checks and record path. A completed run can miss goals. Reuse a key for retries, use a new key for a fresh trial. Background runs survive client exit. Simulator-only pace delays acquisition by 0..600 seconds; fault='sample_gap' truncates a trace.

get_runB

Get current status, terminal reason or measured result by run ID.

cancel_runA

Request cancellation, then poll get_run until terminal to learn the last confirmed state.

list_runsA

List recent IDs and verdicts in this store, most recent first (limit 1..200).

waveformB

Get 1..200 raw samples by offset, including timestamps. Also accepts a portable record path.

reviewC

Offline checksum verification and metric recomputation from run ID, directory or record.json.

compareB

Compare metrics of two completed experiments with matching device, version, action and conditions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target clearly distinct lifecycle stages: device discovery, parameter management, experiment execution, run inspection, waveform access, and offline review. The only mild overlaps are between get_run and review for retrieving/validating results, and between run_experiment and get_run for result access, but descriptions largely clarify these boundaries.

Naming Consistency3/5

Names are readable and mostly snake_case, but conventions are mixed: verb_noun tools like read_parameters and run_experiment coexist with bare nouns such as devices and waveform, and bare verbs such as describe, review, and compare. The pattern is not fully predictable, though it is unlikely to cause misselection.

Tool Count5/5

Twelve tools is well-scoped for a simulated device experiment server, covering discovery, parameter control, execution, monitoring, cancellation, waveform retrieval, and offline validation. Each tool appears to earn its place without obvious redundancy.

Completeness5/5

The surface covers the full experiment lifecycle: discovering and describing devices, reading/applying parameters with history, running experiments, checking/cancelling/listing runs, retrieving waveforms, reviewing records, and comparing completed runs. No major operational gaps are apparent for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues