Skip to main content
Glama

Create toll free verification

create_toll_free_verification
Destructive

Start the carriers' toll-free verification for live toll-free numbers, filled in from the account, its registration, hosted opt-in page and website; any field sent replaces what was filled in. Returns a draft with problems: what the carriers would reject. Nothing goes to the carriers and there is no fee. Submitting needs a paid account (the free credit does not count); otherwise point the person to a local number with 10DLC registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_toll_free_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
einNoThe EIN (US), matching the legal name; elsewhere the business registration number.
cityNoCity.
stateNoState or province code.
streetNoStreet address of the business.
countryNoCountry of the business.
numbersNoYour live toll-free numbers this program texts from, E.164. One per business unless multiple_numbers_reason says why.
websiteNoThe business's website.
use_caseNoWhat the texts are for.
terms_urlNoThe terms page, with the SMS program terms.
help_replyNoThe reply to HELP: names the business and how to reach it. Omit to keep ours.
opt_in_urlNoThe opt-in page. With none of your own we make you a hosted one.
stop_replyNoThe reply to STOP: names the business and says they are unsubscribed. Omit to keep ours.
advertisingNoWhether the messages advertise a product or service.
brand_emailNoThe business's own email, for its customers: the HELP reply and the hosted opt-in page name it.
entity_typeNoThe kind of business.
fortune_500NoThe company is in the Fortune 500.
postal_codeNoZIP or postal code.
privacy_urlNoThe privacy policy page.
volume_basisNoexisting: what it sends today. projecting: an estimate.
business_nameNoThe legal name, as on the IRS EIN letter, optionally with "d/b/a" and the brand your messages carry.
contact_phoneNoA phone number they answer.
monthly_volumeNoHow many texts a month this program sends.
sample_messagesNoAt least two example messages.
number_publishedNoWhere people see this number.
previous_contentNoSample messages from the previous service (not new only).
previous_numbersNoThe numbers it used (not new only).
previous_serviceNoWhere this traffic ran before.
urls_in_messagesNoLinks your messages include, or "None".
use_case_summaryNoWhat the program sends, to whom and why. At least 40 characters.
contact_last_nameNoTheir last name.
contact_first_nameNoFirst name of the person the carriers can contact about this program.
opt_in_descriptionNoHow people opt in, step by step. At least 40 characters.
phones_in_messagesNoPhone numbers your messages include, or "None".
opt_in_screenshot_urlNoA public image of the step where people enter their number and agree. Needed when the opt-in page itself has no phone field, like a later step of a form or an app.
multiple_numbers_reasonNoWhy the program needs more than one number (one per store, say). Required with more than one number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / opt_in_screenshot_url
      Added value: +{
      +  "description": "A public image of the step where people enter their number and agree. Needed when the opt-in page itself has no phone field, like a later step of a form or an app.",
      +  "format": "uri",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing prefill behavior ("filled in from the account, its registration, hosted opt-in page and website"), merge semantics ("any field sent replaces what was filled in"), output nature ("Returns a draft with problems"), and the absence of external effects or fees. That last point is the key behavioral fact for a tool flagged destructiveHint=true, and it is stated plainly.

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 the action and the override rule, and the draft/no-fee caveat follows immediately. It is dense, semicolon-chained prose that takes some unpacking, but no sentence is filler.

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 35-parameter, zero-required tool with no output schema, the description supplies the two things an agent most needs: that everything is optional because of account prefill, and that a draft plus a list of carrier-rejection problems comes back. Nothing essential 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 100% and the per-parameter descriptions are already detailed, so the baseline is 3. The description still adds real value by explaining that omitted fields are auto-filled and sent fields override them, which is parameter behavior the schema cannot express.

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 ("Start the carriers' toll-free verification") and scopes it to "live toll-free numbers." It also distinguishes itself from actual submission ("Nothing goes to the carriers"), so an agent can tell this apart from submit_toll_free_verification without opening any 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 a clear precondition ("Submitting needs a paid account (the free credit does not count)") and an alternative path when that fails ("point the person to a local number with 10DLC registration"). What it lacks is naming the sibling submit tool explicitly, leaving the agent to infer which call performs the actual submission.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.