Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Save Text Registration Details

save_text_registration_details
DestructiveIdempotent

Saves business registration details one answer at a time for carrier text registration, tracking missing fields and keeping saved answers without filing or charging.

Instructions

Save a business's legal name, the name customers know it by (if different), entity type, industry, website, address, authorized contact and what it will text (service only, or service and sales) for its own carrier registration. Business owner, or an admin of the business (such as the partner that created the workspace) preparing it for the owner. Each field holds an answer from the owner; anything omitted is filled from what is already on file (see get_text_registration known). Answers can be saved one at a time: answers given so far are kept, and while questions remain the result lists saved_steps, missing and next_question. The owner can finish here or on the registration page. Never takes the EIN: the owner types it on the registration page returned as setup_url. Each saved answer replaces the value on file for that field. Refused once a filing is already with the carriers. Charges nothing and files nothing.

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_id": "<business_id>"
    },
    "name": "save_text_registration_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
stateNo
streetNoMust match the address the IRS has.
industryNo
brand_nameNoOptional: the name customers know the business by, when it differs from the legal name (a DBA or trade name, as shown on its website). Texts are signed with it.
text_typesNoservice: replies and follow-ups to people who contacted the business. service_and_sales: also lets sales texts go to people who opted in to marketing.
business_idYes
postal_codeNo5-digit ZIP, or ZIP+4.
website_urlNoCarriers check the site loads.
business_typeNo
contact_emailNo
contact_phoneNoA US number the carriers can reach.
contact_titleNoAs the contact signs, e.g. Owner.
contact_last_nameNo
contact_first_nameNo
legal_business_nameNoExactly as on the IRS EIN letter.
contact_job_positionNo

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
savedNo
missingNo
successYesWhether the tool completed successfully
next_stepNo
setup_urlNo
consent_urlNo
saved_stepsNo
registrationNo
next_questionNo
next_step_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it explains the destructive semantics concretely ('Each saved answer replaces the value on file for that field'), the refusal condition once a filing is with carriers, that no EIN is accepted, and that nothing is charged or filed. That reconciles destructiveHint=true with the reassurance that no filing occurs. Minor gap: it does not state permission/auth requirements for the admin path.

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-loads the field list and follows with the behavioral constraints; every sentence carries information. Slight redundancy in restating saved_steps/missing/next_question, which the output schema already exposes, and the actor sentence is wordier than needed.

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?

For a 17-parameter tool with an output schema, the description covers the actor, partial-save behavior, replacement semantics, refusal condition, and cost. Missing only required-field guidance (business_id is the sole required param) and any note on permissions, which are modest gaps given the annotations and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 47% schema coverage, the description compensates by naming the collected fields and adding semantics the schema lacks: omitted fields fall back to what is on file, answers can be saved one at a time, and street must match the IRS address is echoed in the schema. It does not disambiguate contact_title versus contact_job_position or city/state/postal_code expectations.

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 (save) and a concrete resource set (legal name, brand name, entity type, industry, website, address, contact, text types) for carrier registration. It also distinguishes the partial, answer-by-answer nature of the operation from a full submission, so an agent can tell it apart from submit_text_registration without opening schemas.

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 actor and context (business owner or an admin preparing it for the owner) and an explicit exclusion ('Refused once a filing is already with the carriers'). It points at get_text_registration for values already on file, but never names the related completion tool (submit_text_registration) as the alternative for finishing the flow, so routing is only partly explicit.

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

Deploy Server

Other Tools