Skip to main content
Glama
shaag7967

mcp-server-senseca-pro

by shaag7967

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SENSECA_PINNoPIN needed only if the instrument's protected mode is on. No default.
SENSECA_PORTNoSerial port for the Senseca instrument. Equivalent to the --port option. Default is auto-detect.
SENSECA_LOG_LEVELNoLog level for the server. Equivalent to the --log-level option. Default is WARNING.
SENSECA_ALLOW_WRITENoEnable write tools such as set_device_clock and set_location_name. Equivalent to the --allow-write option. Default is off.

Instructions

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

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

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

Tools

Functions exposed to the LLM to take actions

NameDescription
read_temperatureA

Read the current temperature from the Pt100 probe, with unit and UTC timestamp.

read_resistanceA

Read the current Pt100 probe resistance in ohm (about 100 ohm at 0 °C).

sample_temperatureA

Record temperature readings over a period and return statistics plus all samples.

Args: duration_s: Recording time in seconds (max 600). interval_s: Time between readings in seconds (min 0.5, the instrument's update rate).

get_device_infoB

Instrument model, serial number, firmware, clock (UTC) and battery level.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role: two single-value reads for different physical quantities (temperature vs. resistance), one time-series sampling tool, and one device metadata tool. The boundary between read_temperature and sample_temperature is clear because one is a spot reading and the other records over time.

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern: read_temperature, read_resistance, sample_temperature, get_device_info. The verbs are predictable and match the operation type.

Tool Count5/5

Four tools are well-scoped for a Pt100 sensor server with a small, focused read-only domain. Each tool earns its place without redundant operations.

Completeness4/5

The surface covers current temperature, raw resistance, time-series sampling with statistics, and device metadata, which covers the core monitoring workflow. Minor gaps such as calibration or configuration operations are reasonable for a read-only instrument server but prevent a perfect score.

Maintenance

ActivityMaintained
ResponsivenessNo issues