Skip to main content
Glama

octadezx_trigger_voice_call

Initiate a consent-verified outbound AI phone reminder or support follow-up call from your OctaDezx Cloud workspace, with real-time human barge-in for live assistance.

Instructions

Initiate an outbound conversational AI phone reminder or support follow-up call from your OctaDezx Cloud workspace with real-time human barge-in support. Only invoke after verifying consent and call purpose. 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": {
      "phoneNumber": "<phoneNumber>",
      "reason": "<reason>"
    },
    "name": "octadezx_trigger_voice_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesConcise, specific purpose or context brief for the AI voice agent call (3 to 500 characters).
phoneNumberYesDestination phone number in strict E.164 international format (for example, '+14155550199').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / phoneNumber / description
      Previous value: -"Destination phone number in E.164 format"New value: +"Destination phone number in strict E.164 international format (for example, '+14155550199')."
    • addedInput schema / properties / phoneNumber / pattern
      Added value: +"^\\+[1-9]\\d{6,14}$"
    • changedInput schema / properties / reason / description
      Previous value: -"The specific reason or context for the call"New value: +"Concise, specific purpose or context brief for the AI voice agent call (3 to 500 characters)."
    • addedInput schema / properties / reason / maxLength
      Added value: +500
    • addedInput schema / properties / reason / minLength
      Added value: +3
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent, non-destructive, so the safety profile is covered. The description adds real value on top: real-time human barge-in, a consent precondition, the OCTADEZX_API_KEY requirement, and the specific 'requires_api_key' error payload on unauthenticated calls. It stops short of saying what a successful call returns or whether repeat invocations create duplicate calls, which matters for a non-idempotent action.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose, then the precondition, then auth behavior — a sensible ordering with little waste. 'with real-time human barge-in support' is the closest thing to promotional filler, but it does convey a real capability.

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?

For a two-parameter, no-output-schema tool with annotations present, the description covers the essentials: what it does, the consent gate, and the auth failure mode. The remaining gap is post-invocation behavior — no mention of what identifier or status comes back, which is notable for a non-idempotent outbound action.

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%, so both parameters are already fully documented including the E.164 pattern and the 3–500 character bound on reason. The description only gestures at the parameters indirectly through 'verifying consent and call purpose' and adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

The description opens with a specific verb and resource: 'Initiate an outbound conversational AI phone reminder or support follow-up call.' The channel (phone) and the AI-agent nature distinguish it reasonably well from siblings like octadezx_send_customer_reply or octadezx_schedule_appointment, though it never explicitly names an alternative to contrast against.

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?

It gives clear when-to-use context (reminders, support follow-ups) and an explicit gating condition: 'Only invoke after verifying consent and call purpose.' What it lacks is any statement of when NOT to use it or which sibling to pick for adjacent needs (e.g., scheduling vs. immediate dialing).

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