PT5 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_pt5A | Parse a Monsoon Power Monitor PT5 file and return a summary of the captured power data, including sample count, duration, average/min/max current, voltage, and power. |
| get_pt5_channelsA | List the available measurement channels (Main, USB, Aux) in a PT5 file based on its captureDataMask, plus hardware info and sample rate. |
| get_pt5_samplesA | Retrieve sample data from a PT5 file, with optional time range filtering and sample decimation. Returns current (mA) and voltage (V) values. |
| export_pt5_csvB | Export PT5 sample data to a CSV file. Includes timestamps, current (mA), voltage (V), markers, and missing data flags. |
| get_pt5_headerA | Return the raw header and status packet metadata from a PT5 file, including hardware info, calibration data, trigger settings, and scaling factors. |
| analyze_pt5_trendA | Analyze current trend in a PT5 file: detect peaks, periodicity (autocorrelation), trend segments, and anomalies. Useful for identifying periodic power consumption patterns, current spikes, and abnormal power behavior. |
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 6 tools
Each tool has a clearly distinct purpose: analyzing trends, exporting, listing channels, getting header, getting samples, and parsing summary. No overlap, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_pt5_noun pattern (e.g., analyze_pt5_trend, get_pt5_channels). This predictable structure aids agent selection.
With 6 tools, the server is well-scoped for a file format utility. Each tool serves a necessary function without redundancy or unnecessary complexity.
The set covers all essential operations for PT5 files: reading raw data and metadata, parsing summaries, analyzing trends, listing channels, and exporting. No obvious gaps for common use cases.