OptionsFlow 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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_basic_strategiesB | Analyze one legacy options strategy using executable quotes and European Black-Scholes estimates. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly articulated.
The single tool name 'analyze_basic_strategies' follows a clear verb_noun pattern and is syntactically consistent. There are no other names to create inconsistency.
One tool feels very thin for a server named 'OptionsFlow', which implies a broader range of options-related functionality. However, if the intended scope is strictly basic strategy analysis, the single tool is borderline acceptable.
The server only covers basic strategy analysis, leaving gaps for advanced strategies, other analytical features, or workflow operations. Agents needing additional options functionality will hit dead ends.