KaiCalls

Create Customer Workspace

create_customer_workspace

Create a KaiCalls workspace for a business, owned by the business owner's own email (for a partner setting up a customer, or anyone setting up a business for its owner). Returns the checkout link the owner opens to pick a plan and enter their card; the phone line is set up automatically once they pay. Nothing is charged and no number exists until then. The owner signs in with their own email. By default the caller is added as an admin of the new workspace so they can finish setup (get_setup_checklist); pass join_as_admin false to skip. Pass partner_code to credit a referring partner; a partner never passes its own code for its own workspace. Fails if the email already has an account.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No
`state`	No
`plan_id`	No	A plan key from list_plans.
`website`	No
`owner_cell`	No	Owner's cell; calls ring it first once the line is live.
`owner_email`	Yes	The business owner's own email. They own the workspace.
`partner_code`	No	Referring partner's code.
`business_name`	Yes
`business_type`	No
`join_as_admin`	No	Default true.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when success is false
`success`	Yes	Whether the tool completed successfully
`business_id`	No
`owner_email`	No
`checkout_url`	No
`partner_linked`	No	Present for a partner-scoped key: the new business is linked to the partner.
`joined_as_admin`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / partner_linked

Added value: +{
+  "description": "Present for a partner-scoped key: the new business is linked to the partner.",
+  "type": "boolean"
+}

AddedOct 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description adds substantial non-obvious behavior: the tool returns a checkout link, nothing is charged and no number exists until the owner pays, the caller is added as admin by default, and it fails on duplicate email. It even clarifies partner_code semantics (a partner never passes its own code for its own workspace).

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?

Front-loaded with purpose, then lifecycle, then parameter guidance. Dense but nearly every sentence carries decision-relevant information; the 'The owner signs in with their own email' sentence slightly restates the ownership point already made up front.

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 explained, yet the description still usefully signals the checkout link is the payoff. For a 10-parameter mutation with no annotations on permissions/charges, it covers the critical behavioral edges but leaves the five undescribed parameters unaddressed.

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 50% across 10 parameters. The description meaningfully elaborates join_as_admin (default true, admin added so caller can finish setup) and partner_code (referral crediting, never self-referential), but city, state, website, business_type, and business_name receive no explanation in either the description or the schema. Baseline 3 is appropriate given the partial coverage.

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?

Starts with a specific verb+resource ('Create a KaiCalls workspace for a business') and immediately scopes the ownership model ('owned by the business owner's own email'), which separates it from generic setup siblings like set_up_business. An agent can tell what this creates and for whom without opening the schema.

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 context for invocation — a partner setting up a customer, or anyone setting up a business for its owner — plus the explicit failure precondition ('Fails if the email already has an account') and a follow-up pointer (get_setup_checklist). It stops short of naming alternatives (e.g. set_up_business, create_checkout) or stating when-not to use this tool.

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.