Skip to main content
Glama
hail

hail

Official

Preview a US texting registration

preview_sms_application
Read-onlyIdempotent

Preview local or toll-free SMS registration text without filing or charging, returning applicant description, consent flow, and samples so users can catch field or length errors before submission.

Instructions

Preview local or toll-free SMS registration text without filing or charging.

    The response contains the description, consent flow and samples for user review before submission.
    Answers require actual applicant information and consent evidence.
    Field or length errors appear in ``problems``.
    Limits are 100 fields and 64 KiB of combined fields and address.
    A successful preview does not guarantee submission: duplicates, low credit or carrier checks can still prevent it.
    

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": {
      "subject_type": "<subject_type>",
      "fields": "<fields>"
    },
    "name": "preview_sms_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesProposed applicant answers keyed by the field names in ``get_verification_requirements`` with purpose ``sms``.
addressNoThe applicant's address. Give it when the requirements include one; otherwise leave it out.
number_idNoOwned toll-free number ID from ``list_numbers``, for a toll-free preview. Omitted: a US local preview.
subject_typeYesWho the registration is for: the user themselves (``person``) or their company (``business``).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint/idempotent/destructive=false already signal a safe, repeatable read): it discloses that no charge is incurred, that field or length errors surface in `problems`, that there are hard limits of 100 fields and 64 KiB including the address, and that a successful preview does not guarantee submission due to duplicates, low credit, or carrier checks. These are exactly the behavioral caveats an agent needs to set expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, and each following line earns its place by adding a distinct constraint (response shape, data requirement, error surface, size limits, false-positive caveat). No redundant restatement of the title.

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 4-parameter nested-schema tool with an output schema already documenting returns, this description supplies the remaining operational context: cost-free dry run, input size caps, error reporting location, and the conditions under which a green preview still fails. Nothing material is left for the agent to guess.

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 description coverage is 100%, so baseline is 3, and the description adds real meaning on top: the applicant-information requirement for `fields` and the 100-field / 64 KiB cap that constrains what can be sent. It does not elaborate on `subject_type` or `number_id` beyond what the schema already documents, so it stops short of full 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?

States a concrete verb and resource ('Preview ... SMS registration text') plus the two modes it covers (local or toll-free), and the phrase 'without filing or charging' separates it from the actual submission path an agent might otherwise pick. An agent can tell this is a dry-run preview rather than an application write.

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 timing ('for user review before submission') and a prerequisite ('Answers require actual applicant information and consent evidence'), which tells the agent it cannot be called with placeholder data. It never names an explicit alternative or exclusion (e.g. that amend_sms_application is the path once a draft exists), so usage is strongly implied but not fully routed.

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