legacy-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 |
|---|---|
| lookup_customerA | Find customers by number or name fragment; decoded and explained. |
| get_customer_creditC | Credit standing: limit, open exposure, and whether ordering works. |
| check_item_availabilityD | – |
| get_order_statusD | – |
| list_ordersC | Orders by business status name ('pending', 'incomplete', ...). |
| place_orderA | The three-call legacy protocol, wrapped with compensation. HDR_INS validates the customer and creates an 'I' header; each line is inserted with the sequence numbers the backend insists on; FIN totals, decrements stock, and flips the order to pending. If anything fails after the header exists, the incomplete order is DELETED (compensating action) — the backend has no cross-call transactions, so cleanup is the wrapper's job, not the agent's. |
| cancel_orderA | Cancel a pending/released order; the backend restocks the lines. |
| release_holdA | Take a customer off hold — with the PROC_UPD_47 side effect surfaced. The legacy status update ALSO recalculates the credit flag from open exposure. Releasing a hold therefore does NOT guarantee the customer can order; the response says so explicitly instead of letting the agent discover it three calls later. |
| set_customer_statusC | Set a customer's status by business name (active/on_hold/closed). |
| cleanup_incomplete_ordersA | Find and delete orphaned 'I' orders left by crashed legacy writers. |
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 10 tools
Each tool has a clear, distinct purpose: customer lookup, credit, hold, status; order lifecycle (get, list, place, cancel); item availability; and cleanup. No overlapping functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_order_status, lookup_customer), making them predictable and easy to understand.
10 tools cover the core operations of a legacy order/customer system without being excessive or too sparse.
Covers customer management, order lifecycle, inventory check, and cleanup. Missing update/modify order tool, but otherwise well-scoped for the domain.