Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Set Your Client Activity Alerts

agency_clients_set_activity_alerts
Idempotent

Configures which client activity alerts an agency receives—qualified leads, link texts, or clients needing attention—and where to send them via up to five emails or a phone.

Instructions

Chooses which client activity you hear about (qualified leads, a caller texted one of a client's links, a client needing attention) and where those alerts go. With no emails set, alerts go to the agency owners. Requires an agency owner or admin. Changes future alerts only.

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>"
    },
    "name": "agency_clients_set_activity_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoA phone that also gets the alerts by text; null stops the texts.
emailsNoUp to 5 emails for the alerts; an empty list sends them to the agency owners.
eventsNoOn/off switches: qualified_lead, business_link_sent, client_needs_attention.
partnerIdYesThe agency (partner) workspace ID.

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

A3.8/5.0
Behavior4/5

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

Beyond the annotations (idempotent, non-destructive, closed-world write), the description adds genuinely useful behavior: the fallback routing when no emails are set (agency owners), the authorization requirement, and the fact that changes are non-retroactive. Return behavior is left to the output schema, which is acceptable here.

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?

Three short sentences, front-loaded with what is being configured, followed by fallback behavior, permissions, and scope. Nothing is padded and no sentence is redundant.

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 annotations, a full output schema, and 100%-covered parameters, the description covers the remaining agent-facing unknowns: authorization, default recipients, and non-retroactivity. The one meaningful omission is disambiguation from agency_clients_set_client_alerts, which matters for a tool family with two similarly named alert setters.

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 each parameter already carries a description, including the null-stops-texts and empty-list-fallback semantics, so the description mostly restates what the schema provides. It adds the summary framing of the three event switches but no format or edge-case detail beyond the schema, 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?

"Chooses which client activity you hear about ... and where those alerts go" names a specific action and resource, and enumerates the alert categories (qualified leads, link texts, client needing attention). It does not, however, distinguish this from the similarly named sibling agency_clients_set_client_alerts, so an agent must guess which scope applies.

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?

It states a real prerequisite ("Requires an agency owner or admin") and a scope limit ("Changes future alerts only"), which helps decide whether a call is appropriate. But there is no explicit when-to-use-vs-alternative guidance, and the near-duplicate sibling agency_clients_set_client_alerts is never mentioned, leaving the agent to infer the split.

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