Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Set A Client's Lead Alerts

agency_clients_set_client_alerts
Idempotent

Configure a client’s lead alerts: choose all or qualified leads, set alert emails and phones, and control KaiCalls product updates. This updates settings only and sends no messages.

Instructions

Changes one client's lead alerts: every lead or qualified leads only, whether the client gets KaiCalls product updates, and which emails and phones get the alerts. Requires write access to that client (agency owner/admin, or an operator assigned to it, who is also an admin on the client's account). Recorded in the client's change history. Sends nothing.

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": {
      "partnerId": "<partnerId>",
      "businessId": "<businessId>"
    },
    "name": "agency_clients_set_client_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdYesThe agency (partner) workspace ID.
businessIdYesThe client business to change.
leadAlertsNo'qualified' (only leads scored 70 or more), 'all' (every real lead) or 'default'.
alertEmailsNoComma-separated emails that get lead alerts; empty or null clears them.
alertPhonesNoComma-separated phones that get lead alert texts; empty or null clears them.
kaicallsUpdatesEnabledNoWhether the client gets KaiCalls product and account updates; null for the default.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
receiptNo
successYesWhether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses the authorization prerequisite in concrete role terms and two behavioral facts an agent could not infer: the change is recorded in the client's change history, and no notifications are sent as a side effect. These are exactly the mutation traits an agent needs before calling.

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?

Two sentences, front-loaded with the operation and the fields it covers, then the access requirement and side-effect notes. No filler and no repetition of schema detail.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers auth, audit trail and side effects for a 6-parameter mutation. The remaining gap is update semantics: it does not say whether omitted fields are left unchanged or reset, which matters for a settings tool where 'leadAlerts' has no null option.

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%, including the meaning of 'qualified' (score >= 70), null/empty clearing of emails and phones, and the 'default' enum value, so the schema already carries parameter meaning. The description restates the same fields without adding new semantics, 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?

The description names a specific verb (changes) and resource (one client's lead alerts) and enumerates the exact settings touched: alert threshold, KaiCalls product updates, alert emails and phones. That scope implicitly separates it from the similarly named agency_clients_set_activity_alerts, but no sibling is named, so the differentiation is not explicit.

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?

Usage context is clear: call this to modify an existing client's lead-alert configuration, and the caller must hold write access (agency owner/admin or an operator assigned to the client who is also an admin on the client's account). It stops short of naming a fallback tool or stating when not to use it.

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