CallMCP — Phone Call MCP Server

Customize Business Line

set_up_business

Idempotent

Optional line customization: sets the business name and greeting Kai answers with, as the owner requested. Not required to make calls, and never changes payment, usage or fraud limits. Extra business details are optional; no business-qualification questionnaire is needed. An existing business greeting is left unchanged.

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": {
      "business_name": "<business_name>"
    },
    "name": "set_up_business"
  }
}

Input Schema

Name	Required	Description
`website`	No	The business's website, if it has one.
`business_id`	No	The account to set up. Optional when the token reaches one account.
`business_name`	Yes	The business's real name.
`what_you_sell`	No	What the business sells or does, in the owner's words.
`who_kai_will_call`	No	Who the owner wants Kai to call, e.g. other businesses, existing customers, or people who asked for a callback.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`changed`	No
`success`	Yes	Whether the tool completed successfully
`business_id`	No
`persona_mode`	No
`already_business`	No
`greeting_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/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), it discloses scope boundaries: never changes payment, usage or fraud limits, and leaves an existing greeting unchanged. That tells the agent what will not be touched, which is exactly the useful incremental context. It does not describe validation failures or conflicts on re-run, so not a 5.

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 optionality and scope constraints are front-loaded in short clauses with little waste. The 'no business-qualification questionnaire is needed' sentence is defensive and slightly tangential, keeping it from a 5.

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 an output schema present, return values need no explanation, and the description covers mutability scope, idempotent behavior and optionality for a 5-parameter tool. The one gap is that it never clarifies how the 'greeting' relates to the actual parameters.

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 all five parameters are already documented in the schema and the baseline is 3. The description adds only the notion that extra business details are optional; it also references a 'greeting' that has no corresponding parameter, which adds a little ambiguity rather than meaning.

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?

States a concrete verb and resource: sets the business name and the greeting Kai answers with. That is specific enough to separate it from set_up_phone_system or set_business_hours without opening a schema, though it does not name any sibling explicitly.

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?

Gives clear when-not guidance: it is optional, not required to make calls, needs no qualification questionnaire, and extra details are optional. It stops short of naming a concrete alternative tool for the fields it does not cover, so it stops at 4 rather than 5.

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.