legacy2mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orders_GetOrderC | SOAP operation 'GetOrder' on service 'Orders' (adapter: orders). |
| orders_ListOrdersD | SOAP operation 'ListOrders' on service 'Orders' (adapter: orders). |
| orders_GetInventoryC | SOAP operation 'GetInventory' on service 'Orders' (adapter: orders). |
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
GetOrder and ListOrders clearly target order retrieval differently, and GetInventory targets a separate resource. Minor overlap in the 'Get' prefix does not meaningfully confuse selection.
All tools follow a consistent adapter-prefixed PascalCase SOAP operation pattern: orders_GetOrder, orders_ListOrders, orders_GetInventory. The mixed Get/List verbs are minor and reflect the underlying SOAP operation names.
Three tools is borderline thin for an orders service, though it may accurately reflect the exposed legacy SOAP operations. It feels scoped but limited.
The surface only supports reading orders and inventory, with no create, update, cancel, or other lifecycle operations. For an order management domain this is a significant gap that would block common agent workflows.