otparse-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_modbus_pcapB | Parse Modbus/TCP traffic from a PCAP and return transactions plus a basic device inventory. |
| parse_bacnet_pcapC | Parse BACnet/IP traffic from a PCAP and return decoded packets plus a basic device inventory. |
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 2 tools
The two tools have clearly distinct purposes: one parses BACnet/IP traffic and the other parses Modbus/TCP traffic. The descriptions specify different protocols (BACnet vs. Modbus) and outputs (decoded packets vs. transactions), leaving no ambiguity for an agent to misselect between them.
Both tool names follow a consistent verb_noun pattern (parse_bacnet_pcap and parse_modbus_pcap), using the same verb 'parse' and similar noun structures. This predictable naming makes the tool set easy to understand and navigate.
With only 2 tools, the server feels thin for its apparent domain of parsing industrial protocol traffic from PCAPs. While it covers two common protocols, the scope could reasonably include more protocols or related operations, making the count borderline for comprehensive coverage.
The tool set is significantly incomplete for the inferred domain of industrial protocol analysis. It lacks essential operations such as listing available protocols, validating PCAP files, filtering or searching parsed data, and handling other common protocols like DNP3 or OPC UA, which limits agent workflows.