CallMCP — Phone Call MCP Server

Add Team Phone

add_team_phone

DestructiveIdempotent

Add a teammate's (or the owner's) cell to the phones that ring before Kai answers. Idempotent — a cell already listed is reported as already included. Owners and admins are also registered on the admin roster, so calling the business line from that cell reaches the admin secretary; a member only rings. The business's own forwarded-from office line is refused (forwarding_loop) because ringing it would bounce the call straight back. Requires the phone system to be set up first (set_up_phone_system).

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": {
      "phone_number": "<phone_number>"
    },
    "name": "add_team_phone"
  }
}

Input Schema

Name	Required	Description
`name`	No	Display name for this teammate (optional).
`role`	No	member only rings; owner and admin also get admin-secretary access from this cell. Defaults to admin.
`business_id`	No	Business ID (required when the token can access multiple businesses).
`phone_number`	Yes	The cell to add, US format (e.g. (908) 555-1234 or +19085551234).

Output Schema

Name	Required	Description
`code`	No	Present when success is false.
`error`	No	Present when success is false
`member`	No
`success`	Yes	Whether the tool completed successfully
`business_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description explains role consequences (owner/admin get admin-secretary access while member only rings), idempotent reporting behavior, the forwarding_loop refusal case, and the setup prerequisite. These are meaningful operational details that help an agent predict side effects and errors.

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 front-loaded with the main action and then layers in idempotency, role effects, refusal behavior, and the prerequisite. Every sentence contributes useful information without unnecessary repetition.

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 annotations, complete parameter schema, and output schema, the description covers what an agent needs to invoke the tool correctly: purpose, prerequisites, role implications, idempotency, and a key refusal case.

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%, so the parameters are already well documented. The description reinforces role behavior and adds the forwarding-loop constraint on phone_number, but most parameter meaning is already present in the schema.

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 states a specific verb and resource: adding a teammate's or owner's cell to the phones that ring before Kai answers. It does not explicitly differentiate this from the sibling set_owner_phone, so it stops short of full sibling routing guidance.

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?

It gives clear usage context: add a cell that should ring before Kai answers, with role-dependent behavior and the prerequisite that set_up_phone_system must be run first. It also names a when-not condition for the business's own forwarded-from office line, but it does not compare this tool to sibling alternatives.

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.