legacy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/harsha-moparthy/legacy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server