Skip to main content
Glama

octadezx_send_customer_reply

Sends a verified reply into an active OctaDezx customer conversation thread on its originating channel, such as WhatsApp, Instagram, Messenger, Telegram, or Web Widget. Pair with a safety check before sending.

Instructions

Deliver a verified customer care reply into an active OctaDezx Cloud conversation thread across its originating channel (WhatsApp, Instagram, Messenger, Telegram, or Web Widget). Best paired with verify_reply_safety prior to sending. Requires OCTADEZX_API_KEY; returns a structured 'requires_api_key' error payload when unauthenticated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conversationId": "<conversationId>",
      "message": "<message>"
    },
    "name": "octadezx_send_customer_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesFinal verified reply text to send to the customer (up to 4,000 characters).
conversationIdYesUnique identifier of the target OctaDezx customer conversation thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / conversationId / description
      Previous value: -"The customer conversation ID"New value: +"Unique identifier of the target OctaDezx customer conversation thread."
    • addedInput schema / properties / conversationId / minLength
      Added value: +1
    • changedInput schema / properties / message / description
      Previous value: -"The message text to deliver to the customer"New value: +"Final verified reply text to send to the customer (up to 4,000 characters)."
    • addedInput schema / properties / message / maxLength
      Added value: +4000
    • addedInput schema / properties / message / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false; the description adds value beyond them by disclosing the OCTADEZX_API_KEY prerequisite and the specific 'requires_api_key' error payload on unauthenticated calls. It also implies the thread must be 'active' and that channel routing is externally visible, though it says nothing about delivery failures or retry behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action, then the recommended workflow, then the auth/error behavior. No sentence restates the name or title without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering the mutation/safety profile and no output schema to explain, the definition supplies what an agent needs: target scope, required companion step, credential requirement, and error shape. Minor omissions are delivery-failure semantics and whether the sent message is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, including a 4,000-character cap and per-field descriptions, so the baseline is 3. The description adds implicit meaning — the channel is derived from the conversation thread rather than passed as a parameter — but never states this explicitly, so it does not rise above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

'Deliver a verified customer care reply into an active OctaDezx Cloud conversation thread' gives a specific verb plus resource, and the parenthetical enumerates the five target channels, so the action and scope are unmistakable. It does not explicitly state what this tool is *not* for relative to siblings, so it stops just short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Best paired with verify_reply_safety prior to sending' names a concrete companion tool and the ordering constraint, which is real workflow guidance. It gives no explicit when-not-to-use or condition for choosing an alternative sender, so it is clear context rather than full routing logic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.