CallMCP — Phone Call MCP Server

Set Owner Phone

set_owner_phone

DestructiveIdempotent

Saves the owner's own mobile number on the business record (the number Kai texts whenever it takes a call for the owner) 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. In the acquisition flow this step comes before search_available_numbers and buy_number (#2086). 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. declined=true, in place of owner_phone, records a caller who declines to give a number as an inquiry: a KaiCalls lead, with no provisioned business or number.

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": "set_owner_phone"
  }
}

Input Schema

Name	Required	Description
`declined`	No	True (in place of owner_phone) when the caller will not give a reachable number. Records the business as an inquiry lead instead of a provisioned number.
`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

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.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds substantial behavior: US-only validation, E.164 normalization, rejection on invalid numbers, and the ring_first side effect of configuring routing. The gap is that it never states the number replaces an existing owner phone (the actual destructive consequence) or what happens to prior routing.

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?

Purpose and the primary parameter are front-loaded, and the sentences are dense with operational facts. A few clauses, notably the aside about a connected number not proving reachability and the ticket reference, are rationale rather than actionable guidance.

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?

An output schema exists so return values need not be described, and the description covers the two mutually exclusive branches (phone vs. declined) plus validation. It leaves out what an overwrite does to an existing number and any permission or auth prerequisites, which matter for a destructive write.

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%, so each parameter is already documented in the schema. The description restates ring_first (default true, ring-first routing) and the declined-in-place-of-owner_phone conditional requirement with a bit of extra framing ('KaiCalls lead, no provisioned business'), but adds little syntax or meaning the schema lacks.

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: it saves the owner's own mobile number onto the business record, and explains the downstream effect (Kai rings it first, activation/forwarding follow-ups reach a human). It explicitly distinguishes itself from merely connecting a number, so an agent can separate it from buy_number or set_up_phone_system.

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?

Gives explicit sequencing within the acquisition flow ('this step comes before search_available_numbers and buy_number') and names the concrete alternative path via declined=true for callers who will not give a number. The when-to-use and when-to-use-the-other-branch conditions are both spelled out.

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

All CallMCP — Phone Call MCP Server 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.