CallMCP — Phone Call MCP Server

Save Text Registration Details

save_text_registration_details

DestructiveIdempotent

Save a business's legal name, 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

Name	Required	Description
`city`	No
`state`	No
`street`	No	Must match the address the IRS has.
`industry`	No
`text_types`	No	service: 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_id`	Yes
`postal_code`	No	5-digit ZIP, or ZIP+4.
`website_url`	No	Carriers check the site loads.
`business_type`	No
`contact_email`	No
`contact_phone`	No	A US number the carriers can reach.
`contact_title`	No	As the contact signs, e.g. Owner.
`contact_last_name`	No
`contact_first_name`	No
`legal_business_name`	No	Exactly as on the IRS EIN letter.
`contact_job_position`	No

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`saved`	No
`missing`	No
`success`	Yes	Whether the tool completed successfully
`next_step`	No
`setup_url`	No
`consent_url`	No
`saved_steps`	No
`registration`	No
`next_question`	No
`next_step_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations: discloses that each saved answer replaces the value on file, that omitted fields are backfilled from existing data, that partial saves are retained, and that calls are refused after a filing is with the carriers. The 'charges nothing and files nothing' and EIN exclusion notes add safety context the destructive/idempotent hints cannot convey.

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 what is saved, then who, then behavior and constraints; every sentence carries information. It is dense but slightly overstuffed, with the saved_steps/missing/next_question return detail partially redundant given an output schema exists.

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?

For a 16-parameter destructive mutation with an output schema, it covers authorization, partial-save behavior, merge/overwrite semantics, refusal conditions, cost, and what it does not do (EIN, filing). Little an agent needs to call it correctly is missing.

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?

Schema coverage is only 44% across 16 params, but the description enumerates the field groups it accepts (legal name, entity type, industry, website, address, contact, text types) and explains the merge semantics for omitted fields. It does not address format constraints like street matching the IRS record or the state/text_types enums, which the schema handles for only some fields.

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 ('Save a business's legal name, entity type, industry, website, address, authorized contact and what it will text ... for its own carrier registration') and scopes it to a named purpose (carrier registration). The closing line 'files nothing' separates it from filing/submission siblings without naming them.

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?

Clear about who may call it (owner or workspace admin), that answers can be saved incrementally, and that it is refused once a filing is already with the carriers. It points to get_text_registration's `known` for defaults and to setup_url for EIN entry, but it never names an explicit alternative tool for the 'finish the filing' case, so routing to the submit path is only implied.

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.