Skip to main content
Glama
kolivri-voice-mcp

kolivri-voice-mcp

Official
by kolivritech

kolivri_place_call

Place an outbound AI voice call with a defined objective and KYC-verified caller ID; anti-abuse rate limits protect against misuse.

Instructions

Place an outbound AI voice call via Kolivri Engine with KYC verified-caller and anti-abuse rate-limit protection.

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": {
      "to": "<to>",
      "objective": "<objective>",
      "verifiedCallerId": "<verifiedCallerId>"
    },
    "name": "kolivri_place_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination phone number in E.164 (+972541234567) or Israeli format (054-1234567).
contextNoOptional structured variables passed to the voice prompt.
languageNoConversation language code (defaults to "he").he
objectiveYesClear mission/objective for the AI voice agent during the call.
webhookIdNoKolivri campaign/engine webhook ID (defaults to KOLIVRI_WEBHOOK_ID env var).
contactNameNoOptional name of the person being called.
verifiedCallerIdYesKYC-verified outbound caller ID registered to your Kolivri account (E.164 or Israeli format).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/open-world/non-idempotent safety profile, so the description's added value is the KYC-verified caller requirement and the anti-abuse rate limiting — real operational context an agent needs before invoking. It does not disclose what is returned, whether calls are billed, or what happens on rate-limit rejection.

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?

A single sentence with the action front-loaded and the two key constraints trailing. Every clause carries information; nothing is redundant with the title or annotations.

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

Completeness3/5

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

For a 7-parameter mutation tool with a nested object and no output schema, the description covers inputs implicitly but never says what a successful call returns (e.g., a call ID for later status checks). Since no output schema exists, that return-value gap is a real omission.

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 description coverage is 100% and each parameter, including the nested context object and the language enum, is documented in the schema itself. The description adds no meaning beyond that, 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?

States a specific verb and resource: 'Place an outbound AI voice call via Kolivri Engine'. This is clearly distinct from read-only siblings like kolivri_get_call_status. It stops short of explicitly naming a sibling or contrasting scope, so it doesn't reach 5.

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

Usage Guidelines3/5

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

Usage is implied by the outbound-call framing and by the embedded prerequisite of a KYC-verified caller ID, but there is no explicit 'use this when...' guidance, no exclusions, and no pointer to the sibling tools for checking call status or previewing costs.

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