Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Configure Staff Alerts

configure_staff_alerts
DestructiveIdempotent

Set the phones, emails, escalation rules, and lead alert thresholds that KaiCalls staff alerts use. Each list you send replaces the saved list, so read current settings first and send every entry to keep.

Instructions

Save the business's alert contacts and post-call escalation rules. Read get_operational_settings first: each list you send (notification_phone, notification_email, escalation_rules) replaces the whole saved list, so include the entries to keep. Listed phones get after-call summary texts and escalation texts (one-recipient alerts go to the first phone); listed emails get escalation emails. lead_alerts chooses every lead or qualified leads only, and kaicalls_updates_enabled turns KaiCalls product and setup mail on or off (both default to quiet for a business a partner set up). Saving does not prove delivery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "configure_staff_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoValidate and show the proposed settings without writing.
business_idNoBusiness ID (optional only when the token has exactly one accessible business)
lead_alertsNo'qualified' = alert only on leads scored 70+ and stop the per-call 'a call came in' texts and emails; 'all' = every real lead; 'default' = the account default (qualified for a business set up by a partner, else all).
escalation_rulesNoPost-call escalation rules checked against each finished call. Replaces the saved rules. Each rule is { id?, when, then, enabled? }.
sms_notificationsNoEnable or disable SMS staff alerts for this business.
notification_emailNoEmail addresses that get escalation emails. Replaces the saved list. Comma-separated string or array.
notification_phoneNoPhones that get alert texts; the first also gets one-recipient alerts. Replaces the saved list. Comma-separated string or array.
email_notificationsNoEnable or disable email staff alerts for this business.
lead_alert_min_scoreNoExact lead score bar for alerts (0 = every lead). Overrides lead_alerts. null = account default.
kaicalls_updates_enabledNoKaiCalls product news, setup tips, weekly summaries and account nudges to this business. Off by default for a business set up by a partner. Billing receipts and team invitations always go. null = account default.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
dry_runNo
successYesWhether the tool completed successfully
settingsNo
business_idNo
current_settingsNo
proposed_settingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the operational consequence: every list sent replaces the saved list wholesale, so omitted entries are lost. It further discloses recipient routing (first phone gets one-recipient alerts), quiet-by-default behavior for partner-set-up businesses, and the caveat that 'Saving does not prove delivery.'

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?

Front-loads the action, then the prerequisite and the replacement hazard before per-field notes. Dense but nearly every clause carries information; a few details (one-recipient alert routing) duplicate the schema and could be trimmed.

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

Completeness5/5

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

For a 10-parameter, all-optional, destructive write tool with an output schema and full annotation coverage, the description supplies the three things the structured data cannot: read-first workflow, list-replacement semantics, and the limits of what a successful save proves.

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% and the schema already documents the key semantics, including the first-phone rule, the lead_alerts enum meanings, and the partner-default behavior. The description restates several of these rather than adding new meaning, so it sits at the baseline for a fully documented schema.

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 and resource: 'Save the business's alert contacts and post-call escalation rules.' It also implicitly distinguishes itself from the read counterpart by naming get_operational_settings as the prerequisite step, so an agent knows this is the write side of the settings pair.

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?

Gives a clear prerequisite ('Read get_operational_settings first') and explains the replacement condition that governs correct usage. It does not name an alternative write path or state when not to use it, but the read-before-write guidance is explicit and actionable.

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