KaiCalls

Set Owner Phone

set_owner_phone

DestructiveIdempotent

Call this BEFORE search_available_numbers/buy_number (#2086) — do not find or buy a number for someone who has not given a reachable number. Ask for it as "the number I'll text you at whenever I take a call for you", not as a generic form field. Saves the owner's own mobile number on the business record so Kai can ring it first and so activation/forwarding follow-ups can reach a human — connecting a number alone does not prove the owner can be reached. US numbers only; normalized to E.164 and rejected if it cannot be validated as a US mobile/landline number. When ring_first is true (default), also configures ring-first routing so calls hit this cell before overflowing to the secretary — the same path used at signup. If the caller declines to give a number, pass declined=true instead of owner_phone: this records the signup as an inquiry (a KaiCalls lead, not a provisioned business+number) and you must not call find_number/buy_number for this business afterward.

Input Schema

TableJSON Schema

Name	Required	Description
`declined`	No	Set true (instead of owner_phone) when the caller will not give a reachable number. Records the business as an inquiry lead instead of a provisioned number — never buy a number after this.
`ring_first`	No	When true (default), ring this number first and overflow to the secretary. When false, only saves the number.
`business_id`	No	Business ID (optional only when the token can access exactly one business).
`owner_phone`	No	The owner's own mobile number, US format (e.g. (908) 555-1234 or +19085551234). Required unless declined is true.
`contact_name`	No	Only used with declined=true: the caller name, for the inquiry record.
`contact_email`	No	Only used with declined=true: an email for the inquiry record, if given.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when success is false
`status`	No
`success`	Yes	Whether the tool completed successfully
`next_step`	No
`business_id`	No
`ring_first_status`	No
`owner_phone_masked`	No
`ring_first_applied`	No
`owner_phone_present`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 26, 2026

addedInput schema / properties / contact_email

Added value: +{
+  "description": "Only used with declined=true: an email for the inquiry record, if given.",
+  "type": "string"
+}

addedInput schema / properties / contact_name

Added value: +{
+  "description": "Only used with declined=true: the caller name, for the inquiry record.",
+  "type": "string"
+}

addedInput schema / properties / declined

Added value: +{
+  "description": "Set true (instead of owner_phone) when the caller will not give a reachable number. Records the business as an inquiry lead instead of a provisioned number — never buy a number after this.",
+  "type": "boolean"
+}

changedInput schema / properties / owner_phone / description

Previous value: -"The owner's own mobile number, US format (e.g. (908) 555-1234 or +19085551234)."New value: +"The owner's own mobile number, US format (e.g. (908) 555-1234 or +19085551234). Required unless declined is true."

changedInput schema / required

Previous value: -[
-  "owner_phone"
-]New value: +[]

addedOutput schema / properties / owner_phone_present
```
Added value: +{
+  "type": "boolean"
+}
```

AddedSep 10, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true, but the description goes further, explaining the declined path and its irreversible consequences ('you must not call find_number/buy_number for this business afterward'). It also discloses validation rules (US only, E.164 normalization), ring-first routing, and the effect on signup status. No contradiction with annotations; the description enriches the behavioral context.

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?

The description is dense but efficient, front-loading the most critical warning (ordering requirement) and structuring content logically: order, purpose, details, declined case. Every sentence earns its place, providing actionable guidance without fluff.

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?

Given the complexity (6 parameters, critical ordering, two mutually exclusive paths), the description is complete. It covers validation, normalization, ring-first behavior, declined handling, and the consequences of each path. An output schema exists, so return values are not needed. An agent can confidently invoke this tool correctly based on the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 100%, the description adds substantial semantic meaning beyond the schema. It explains the relationship between owner_phone and declined, clarifies the ring_first default, and even advises on how to phrase the question to the caller. This goes far beyond the basic field descriptions.

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?

The description clearly states the tool's purpose: setting the owner's phone number on a business record, with explicit differentiation from sibling tools like search_available_numbers and buy_number. It uses a specific verb ('set') and resource ('owner phone'), and immediately explains when it should be called relative to other operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: 'Call this BEFORE search_available_numbers/buy_number (#2086)'. It also explains when not to use it (declined case) and prohibits subsequent number purchasing. This is model usage guidance with clear exclusions and alternatives.

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

All KaiCalls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.