Skip to main content
Glama
theYahia

@theyahia/voximplant-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

start_call

Start an outbound call through Voximplant by providing a routing rule and destination, passing the destination to the VoxEngine scenario via customData.

Instructions

Инициировать исходящий звонок через Voximplant по правилу маршрутизации. Номер назначения передаётся сценарию через customData — сценарий VoxEngine должен его обработать.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesID правила маршрутизации (StartScenarios запускает его сценарий)
caller_idNoCaller ID — передаётся сценарию в customData (StartScenarios не имеет отдельного параметра caller_id).
destinationYesНазначение звонка (номер E.164, SIP URI или внутренний extension). Передаётся сценарию через customData: сценарий читает VoxEngine.customData() и инициирует звонок (callPSTN/callPBX/callSIP).
script_custom_dataNoПереопределить customData целиком. Если задано — destination/caller_id игнорируются.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / caller_id / description
      Previous value: -"Номер в Caller ID (если не указан — берётся из правила)"New value: +"Caller ID — передаётся сценарию в customData (StartScenarios не имеет отдельного параметра caller_id)."
    • changedInput schema / properties / destination / description
      Previous value: -"Номер назначения для звонка"New value: +"Назначение звонка (номер E.164, SIP URI или внутренний extension). Передаётся сценарию через customData: сценарий читает VoxEngine.customData() и инициирует звонок (callPSTN/callPBX/callSIP)."
    • addedInput schema / properties / destination / minLength
      Added value: +1
    • changedInput schema / properties / rule_id / description
      Previous value: -"ID правила маршрутизации для звонка"New value: +"ID правила маршрутизации (StartScenarios запускает его сценарий)"
    • changedInput schema / properties / script_custom_data / description
      Previous value: -"Кастомные данные для сценария VoxEngine"New value: +"Переопределить customData целиком. Если задано — destination/caller_id игнорируются."
  2. First observedv1.2.3

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It explains that the destination is passed via customData to the VoxEngine scenario, which must process it, and that script_custom_data can override. However, it does not disclose side effects (e.g., call cost, required permissions) or the expected outcome of the call initiation.

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?

The description is a single, front-loaded sentence that states the purpose and key data-flow detail. No redundant wording or filler. It is optimally concise for the information it conveys.

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

Completeness2/5

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

For a tool that initiates a call, with no output schema and no annotations, the description is too sparse. It does not mention the return value (e.g., call ID, success status), error conditions, or any post-call behavior. An agent would be unsure what the tool actually returns or how to interpret the result.

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

Parameters4/5

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

Schema description coverage is 100%, so each parameter is documented in detail. The description adds value by explaining how parameters interrelate: destination and caller_id are transmitted via customData, and script_custom_data overrides them. This provides context beyond the individual parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool's action: initiating an outbound call via Voximplant using a routing rule. It is distinct from sibling tools, which are mostly get_* or send_sms operations. The purpose is unambiguous and the tool name is not merely restated.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus others, no mention of prerequisites (such as having a rule or scenario configured), and no exclusions. The description implies it is the tool for starting calls but does not help an agent decide between it and alternatives.

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

Deploy Server

Other Tools