mcp-server-saxo-openapi
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 |
|---|---|
| search_saxo_endpointsC | Search for Saxo Bank OpenAPI endpoints by keyword. |
| get_saxo_endpoint_specC | Get parameter specs and JSON samples for a Saxo Bank OpenAPI endpoint. |
| get_saxo_schema_specC | Get nested schema parameters referenced from endpoint specs. |
| get_saxo_workflow_guideC | Get workflow guidance for complex Saxo operations (close_position, if_done_oco). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_pitfalls | Returns the Saxo Bank OpenAPI pitfalls and workarounds guide for AI agents. |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: endpoint specs, schema specs, workflow guides, and search. There is no overlap in functionality.
Three tools use 'get_saxo_' prefix while one uses 'search_saxo_'. The pattern is mostly consistent, with a minor deviation.
Four tools are well-suited for this niche API documentation server, providing essential operations without unnecessary clutter.
The set covers endpoint specs, schema details, workflow guidance, and search. A minor gap could be a tool for listing all endpoints, but search largely compensates.