Skip to main content
Glama
kolivri-voice-mcp

kolivri-voice-mcp

Official
by kolivritech

kolivri_preview_roi

Read-onlyIdempotent

Calculate missed-call revenue loss from weekly unanswered calls and average deal value, then recommend the matching Kolivri plan.

Instructions

Calculate SMB missed-call revenue loss and recommend the matching Kolivri unified plan (Starter $69 / ₪247, Business $139 / ₪479, Pro $249 / ₪880).

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": {
      "missedCallsPerWeek": "<missedCallsPerWeek>",
      "avgDealValueIls": "<avgDealValueIls>"
    },
    "name": "kolivri_preview_roi"
  }
}

Input Schema

NameRequiredDescriptionDefault
avgDealValueIlsYesAverage customer transaction or deal value in ILS (₪).
closeRatePercentNoPercentage of answered leads that convert into paying customers (0-100, default 25).
missedCallsPerWeekYesEstimated number of unanswered or missed inbound calls per week.
aiRecoveryRatePercentNoPercentage of missed calls recovered/qualified by Kolivri AI (0-100, default 60).
estimatedMonthlyCallsNoOptional total monthly AI call volume override used for plan sizing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context by naming the three plan tiers and their dual-currency prices, but says nothing about how the recommendation is derived, whether results are deterministic, or what the returned recommendation looks like.

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?

A single front-loaded sentence that leads with the core calculation before the pricing detail. The tier prices are dense but arguably load-bearing for an ROI tool; nothing is wasteful, though the currency/symbol pairing makes it slightly cluttered.

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 read-only calculator with full schema coverage and no output schema, the description covers the input side adequately. However, it never characterizes the output — the loss figure versus the recommended plan — leaving the agent to guess the response shape for a tool whose entire value is its returned recommendation.

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 all five parameters, including defaults for closeRatePercent and aiRecoveryRatePercent, are already documented in the schema. The description adds no parameter-level meaning beyond pricing context, so the baseline of 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 ('Calculate') and resource ('SMB missed-call revenue loss'), plus the secondary action of recommending a plan tier. It is clearly distinguishable from the carrier-forwarding, call-status, and place-call siblings. It stops short of tying itself explicitly to any sibling, which keeps it at 4 rather than 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 only implied: an agent can infer this is a pre-sales ROI estimator, but there is no statement of when to call it versus the placement or status tools, nor any prerequisite or exclusion. The pricing tiers hint at a quoting context but do not constitute guidance.

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