fix-protocol-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_fix_messageA | Decode a raw FIX message (SOH, '|', or '^' delimited) into tag/name/value/meaning fields. |
| validate_fix_messageB | Validate a FIX message: field order, header, BodyLength/CheckSum, and required fields per MsgType. |
| build_fix_messageB | Build a FIX message from field names/values (e.g. Side='Buy'). BodyLength and CheckSum are computed. |
| explain_fix_tagA | Look up a FIX tag's field name, data type, and enumerated values. |
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 4 tools
Each tool targets a distinct FIX operation: building, explaining tags, parsing, and validating. No functional overlap exists.
All tool names follow a clear verb_noun pattern with underscores (build_fix_message, explain_fix_tag, etc.), ensuring predictability.
Four tools is well-scoped for a FIX protocol assistant, covering core tasks without excess or deficiency.
The set covers the full lifecycle of FIX message handling: construction, parsing, validation, and tag lookup. No obvious gaps for the intended purpose.