metashunt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METASHUNT_BAUD | No | Baud for the serial link (cosmetic over USB-FS) | 1000000 |
| METASHUNT_LOG_DIR | No | Where sessions are persisted | ~/.metashunt/logs |
| METASHUNT_RING_SIZE | No | In-memory raw ring capacity (samples) | 262144 |
| METASHUNT_IDLE_TIMEOUT | No | Reserved (idle detection) | 2.0 |
| METASHUNT_DEC_ABS_MIN_MA | No | Default abs-min decimation threshold (mA) | 0.00003 |
| METASHUNT_DEC_MAX_POINTS | No | Default max_points | 1000 |
| METASHUNT_DEC_THRESHOLD_PCT | No | Default decimation threshold percent | 1.0 |
| METASHUNT_SELFTEST_SIMULATE | No | Set to 1 to force scripts/selftest.py into offline mode | (unset) |
| METASHUNT_SERIAL_READ_TIMEOUT | No | Per-read serial timeout (s) | 0.1 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| metashunt_statusB | Return connection and capture status. |
| metashunt_start_captureA | Begin continuous (streaming) capture into a named session. Returns the session name used. Sampling continues in the background until
:func: |
| metashunt_stop_captureA | Stop recording. The device keeps measuring; the server just stops listening. The current session is finalized on disk. |
| metashunt_stream_nowB | Return the most recent samples from the live ring, decimated.
|
| metashunt_burstC | Perform a high-rate device burst read.
|
| metashunt_set_triggerB | Add/replace a host-side trigger watching the live stream for a crossing
above |
| metashunt_list_triggersD | – |
| metashunt_remove_triggerD | – |
| metashunt_list_sessionsA | List persisted capture sessions (from .npz/.json logs). |
| metashunt_load_sessionC | Load a session from disk, decimate, and return its data + summary. |
| metashunt_slice_logC | Load a time window |
| metashunt_measurement_statsA | Compute aggregate statistics (count/mean/std/min/max) over a session window without transferring the full dataset. |
| metashunt_delete_sessionD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct operation: status, capture start/stop, streaming, burst reads, trigger management, and session persistence/analysis. Even tools with empty descriptions (e.g., list_triggers, delete_session) have unambiguous names that clearly convey their purpose.
All tools share the metashunt_ prefix and mostly follow a verb_noun pattern (start_capture, set_trigger, list_sessions). A few exceptions like 'status' (noun) and 'burst' (verb) deviate slightly, but the overall pattern remains predictable and readable.
With 13 tools, the server is well-scoped for a device control and data analysis role. Each tool serves a clear, non-redundant function, covering capture, streaming, triggers, and session management without bloat.
The tool surface covers the core lifecycle: capture start/stop, live data retrieval, burst reads, trigger configuration, and session persistence with loading, slicing, statistics, and deletion. Minor gaps like device configuration or metadata retrieval exist, but agents can accomplish primary workflows without dead ends.