OctaDezx MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTADEZX_API_KEY | Yes | Your OctaDezx API key | |
| OCTADEZX_ENDPOINT | No | The hosted MCP server endpoint URL | https://octadezx.com/mcp |
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 |
|---|---|
| octadezx_list_conversationsA | List recent and escalated customer care conversations across WhatsApp, Instagram, Telegram, and Web. |
| octadezx_send_customer_replyC | Transmit a contextual customer care response directly into the active customer thread. |
| octadezx_verify_orderC | Verify order status and check server-side verified pricing against saved catalog records. |
| octadezx_schedule_appointmentC | File an appointment or booking request and verify team availability in the calendar. |
| octadezx_trigger_voice_callC | Initiate an outbound conversational phone call with live human barge-in interruption. |
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 5 tools
Each tool targets a distinct action (list, schedule, reply, call, verify) on a distinct resource, so misselection is unlikely. The only mild overlap is between send_customer_reply and trigger_voice_call, both being outbound customer communication, but the channel difference (text thread vs. phone call) is stated clearly.
All five tools use the same namespace prefix and a strict snake_case verb_noun pattern (list_conversations, schedule_appointment, send_customer_reply, trigger_voice_call, verify_order). Naming is fully predictable.
Five tools is a tight, well-scoped set for an omnichannel customer care agent, with each tool earning its place. It sits at the low end of the comfortable 3-15 range, leaving little room for edge-case operations.
The surface covers reading conversations, replying, booking, calling, and order verification, but has notable gaps: no way to update/escalate/close a conversation, and no reschedule or cancel for appointments. Agents will hit dead ends on common lifecycle operations like handoff and booking modification.