KaiCalls

Set Up Phone System

set_up_phone_system

DestructiveIdempotent

Turn the business's number into a hosted phone system: Kai is installed as extension 700, the owner's mobile joins a team ring group, and a dial plan rings the team first and hands the call to Kai when nobody picks up. Idempotent and resumable — a re-run reuses everything already created and reports it under reused. Needs a complete US street address on file (the emergency-services and tax location) and the owner's mobile: when either is missing the tool fails with code missing_address or missing_owner_mobile plus required_field and next_action saying exactly what to collect — pass it back as business_address or owner_mobile. Returns the status shape (extension, ring group, dial plan ids, the phone-system line) and next_step, the one line to relay to the owner (forward your line here / dial 700 from any office phone). Mirrors POST /api/v1/phone-system action=provision.

Input Schema

TableJSON Schema

Name	Required	Description
`persona`	No	Which phones the business runs on, if the owner said: cell_only (just the owner's cell) or office (desk phones / an existing office line that will forward in). Shapes next_step; optional.
`business_id`	No	Business ID (required when the token can access multiple businesses).
`owner_mobile`	No	The owner's own mobile number (US). Optional when set_owner_phone already saved one; required when the last attempt returned missing_owner_mobile.
`business_address`	No	The business street address to save before provisioning. Optional when a complete address is already on file; required when the last attempt returned missing_address.

Output Schema

TableJSON Schema

Name	Required	Description
`ids`	No
`code`	No	Present when success is false.
`line`	No	The phone-system line (E.164), if a number is attached.
`error`	No	Present when success is false
`reused`	No
`created`	No
`success`	Yes	Whether the tool completed successfully
`warnings`	No
`next_step`	No	The one line to relay to the owner.
`business_id`	No
`next_action`	No	What to collect and how to retry, when blocked.
`provisioned`	No
`kai_extension`	No
`required_field`	No	Present when setup is blocked on a missing input.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true (the description reinforces the re-run reuse behavior, which is an addition). It discloses failure modes and error codes (missing_address / missing_owner_mobile), return shape, and the idempotent/reused behavior, which is valuable beyond the structured annotations.

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?

The description is long but each sentence earns its place: it covers the provisioning behavior, error handling, return shape, and the API mapping. It is front-loaded with the core action, though it's somewhat dense and could be tightened.

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?

The description covers preconditions (address + mobile on file), failure modes with exact error codes, return shape, next_step guidance, the persona parameter's effect, and the API endpoint it mirrors. Even without a separate output schema visible, the agent has enough to invoke and handle the response correctly.

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 high (business_address, owner_mobile, persona are all described). The description adds context by tying parameters to failure codes (missing_address / missing_owner_mobile), but it mostly reinforces the schema descriptions rather than adding new semantics beyond noting the `reused` report and the next_action flow.

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 states a specific verb ('Turn ... into'), resource ('hosted phone system'), and detailed behavior (installs extension 700, team ring group, dial plan). It clearly distinguishes this tool from siblings like order_phone_number by describing the full provisioning workflow rather than just purchasing a number.

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?

The description gives strong contextual guidance: it says the tool needs a complete US street address and the owner's mobile, explains when it failseb and names the endpoint it mirrors. It doesn't explicitly state 'use this instead of order_phone_number when you want to provision a hosted system', so it misses a direct alternative comparison, but the context is clear enough.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.