odse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODSE_WORKSPACE | No | Absolute path used when resolving relative payload_file values. If omitted, the server uses its process working directory. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ConvertToODSEA | Convert raw OEM energy telemetry (CSV/JSON text or file) into ODS-E energy-timeseries records using odse.transformer.transform. Optionally auto-detect the OEM when source is omitted. |
| ListSupportedOEMsA | List OEM source keys supported by the installed odse package, plus the odse package version. |
| ValidateODSERecordB | Validate a JSON array of ODS-E records using odse.validate_batch (package semantics). |
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 3 tools
Each tool has a clearly distinct purpose: conversion, listing supported OEMs, and validation. There is no functional overlap between them, making misselection unlikely.
All tool names follow the same Verb+Object pattern (ConvertTo, ListSupported, Validate) with consistent PascalCase. The naming convention is uniform and predictable.
With 3 tools, the server is well-scoped for its stated purpose of converting and validating ODS-E records. Each tool is necessary and the count is within the ideal 3-15 range.
The tool surface covers the core workflow: convert data, list supported sources, and validate output. There are no obvious missing operations for the declared domain of ODS-E conversion and validation.