Skip to main content
Glama
kolivri-voice-mcp

kolivri-voice-mcp

Official
by kolivritech

kolivri_carrier_forwarding_codes

Read-onlyIdempotent

Generate GSM/carrier call-forwarding dial codes for Israeli telecom carriers to route missed or busy calls to an AI reception number, with ##002# reset.

Instructions

Generate 30-second GSM/carrier call-forwarding dial codes (61, 67, 62, 21 and ##002# reset) for Israeli telecom carriers.

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": {
      "carrier": "<carrier>",
      "targetNumber": "<targetNumber>"
    },
    "name": "kolivri_carrier_forwarding_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierYesIsraeli carrier identifier (partner, pelephone, cellcom, hot_mobile, golan, 019, we4g, bezeq).
ringSecondsNoRing timeout in seconds before forwarding on no-answer (5, 10, 15, 20, 25, or 30).
targetNumberYesKolivri AI reception phone number to forward missed/busy calls to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is covered. The description adds the concrete code families and the ##002# reset, which is useful context, but it omits how the codes are returned and why a reset code is included. Its claim of '30-second' codes also conflicts with the configurable ring timeout in the schema.

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 front-loaded sentence with the verb, the resource, and concrete code examples; no filler. The only questionable element is the '30-second' qualifier, but structurally the definition is tight.

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 simple, annotation-covered computation with fully documented parameters, the definition is serviceable but leaves two things an agent needs: there is no output schema, so the description should say what a returned code looks like and what to do with it, and the 'Israeli carriers' framing is incomplete against the broader enum.

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%, so the schema already documents carrier, targetNumber, and the ringSeconds range, making 3 the baseline. However, the description's '30-second' phrasing works against the schema, which allows ringSeconds from 5 to 30 with a default of 15, risking an agent assuming a fixed timeout. It also calls the tool Israeli-carrier-only while the enum includes us_gsm, verizon, uk_eu_gsm, au_global, and twilio_sip.

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?

States a specific verb ('Generate') plus the exact resource ('GSM/carrier call-forwarding dial codes') and enumerates the code families (*61*, *67*, *62*, *21*, ##002# reset). This is clearly distinguishable from siblings like kolivri_place_call or kolivri_get_call_status, which operate on live calls rather than producing dial strings.

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 the setup step for forwarding missed/busy calls, but the description never states when to reach for it versus kolivri_place_call or kolivri_get_call_status, nor any prerequisite (e.g., that the returned codes must be dialed on the handset).

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