retail-order-sync-hub
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| _get_order_statusC | Return the current status of an order from the silver layer. |
| _trace_orderB | Return a cross-source timeline for an order: inbound webhooks → outbox pushes → silver state. |
| _get_dlq_depthC | Return the number of orders currently stuck in the DLQ. |
| _get_sla_metricsA | Return SLA metrics (avg, p50, p95 sync time in seconds) for a marketplace from the BigQuery gold layer. |
| _find_failed_ordersC | Find orders that were created but never successfully synced to a marketplace. |
| _replay_dlq_messageB | Reset a DLQ outbox entry back to pending so the worker retries it. Scope: dlq.replay. Audited. |
| _retry_failed_syncC | Force re-enqueue of an order into the outbox for all active adapters. Scope: outbox.retry. Audited. |
| _drain_dlqA | List (dry_run=True) or bulk-reset (dry_run=False) all DLQ outbox entries. Scope: dlq.admin. Audited. |
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/JulioPradenas/retail-order-sync-hub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server