Skip to main content
Glama

Hail Communication for AI

Preview a US texting registration

preview_sms_application
Read-onlyIdempotent

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.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
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. Changed2 schema fields changed
    • changedInput schema / properties / address / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "city": {
      -        "description": "City or locality.",
      -        "title": "City",
      -        "type": "string"
      -      },
      -      "country_code": {
      -        "description": "ISO alpha-2 address country.",
      -        "title": "Country Code",
      -        "type": "string"
      -      },
      -      "customer_name": {
      -        "description": "Name associated with the address.",
      -        "title": "Customer Name",
      -        "type": "string"
      -      },
      -      "postal_code": {
      -        "description": "Postal or ZIP code.",
      -        "title": "Postal Code",
      -        "type": "string"
      -      },
      -      "region": {
      -        "description": "State, province or region.",
      -        "title": "Region",
      -        "type": "string"
      -      },
      -      "street": {
      -        "description": "Street address.",
      -        "title": "Street",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "customer_name",
      -      "street",
      -      "city",
      -      "region",
      -      "postal_code",
      -      "country_code"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "city": {
      +        "description": "City or town of the street address, as written on mail sent there.",
      +        "title": "City",
      +        "type": "string"
      +      },
      +      "country_code": {
      +        "description": "ISO alpha-2 address country.",
      +        "title": "Country Code",
      +        "type": "string"
      +      },
      +      "customer_name": {
      +        "description": "Name associated with the address.",
      +        "title": "Customer Name",
      +        "type": "string"
      +      },
      +      "postal_code": {
      +        "description": "Postal or ZIP code of the street address, such as `94103`.",
      +        "title": "Postal Code",
      +        "type": "string"
      +      },
      +      "region": {
      +        "description": "State, province or region.",
      +        "title": "Region",
      +        "type": "string"
      +      },
      +      "street": {
      +        "description": "Street address.",
      +        "title": "Street",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "customer_name",
      +      "street",
      +      "city",
      +      "region",
      +      "postal_code",
      +      "country_code"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / address / anyOf
      Previous value: -[
      -  {
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "city": {
      +        "description": "City or locality.",
      +        "title": "City",
      +        "type": "string"
      +      },
      +      "country_code": {
      +        "description": "ISO alpha-2 address country.",
      +        "title": "Country Code",
      +        "type": "string"
      +      },
      +      "customer_name": {
      +        "description": "Name associated with the address.",
      +        "title": "Customer Name",
      +        "type": "string"
      +      },
      +      "postal_code": {
      +        "description": "Postal or ZIP code.",
      +        "title": "Postal Code",
      +        "type": "string"
      +      },
      +      "region": {
      +        "description": "State, province or region.",
      +        "title": "Region",
      +        "type": "string"
      +      },
      +      "street": {
      +        "description": "Street address.",
      +        "title": "Street",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "customer_name",
      +      "street",
      +      "city",
      +      "region",
      +      "postal_code",
      +      "country_code"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / address / description
      Previous value: -"Applicant address with ``customer_name``, ``street``, ``city``, ``region``, ``postal_code`` and ``country_code``, when the requirements include one."New value: +"The applicant's address. Give it when the requirements include one; otherwise leave it out."
    • changedInput schema / properties / subject_type / description
      Previous value: -"The actual applicant: ``person`` or ``business``."New value: +"Who the registration is for: the user themselves (``person``) or their company (``business``)."
    • addedInput schema / properties / subject_type / enum
      Added value: +[
      +  "person",
      +  "business"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavior beyond that: no filing or charge, field/length errors surface in ``problems``, hard limits of 100 fields and 64 KiB, and the caveat that a successful preview does not guarantee submission due to duplicates, credit or carrier checks.

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?

The core purpose and the 'no filing or charge' guarantee are front-loaded, then supporting constraints follow in short standalone lines. Every sentence carries distinct information (limits, problems key, non-guarantee), with no padding.

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?

With an output schema present, the description need not document return values, yet it still flags the ``problems`` field and the shape of a successful response (description, consent flow, samples). Combined with the limits and the submission caveat, an agent has enough to call this correctly; only sibling routing guidance is thin.

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 100%, including descriptions for fields, address, number_id, subject_type and llm_model, so the schema carries parameter meaning. The description adds only indirect hints (that answers must be real applicant data and that field names come from get_verification_requirements), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb (preview) and resource (local or toll-free SMS registration text) and adds the key scope qualifier 'without filing or charging,' which separates it from amend_sms_application and a real submission. It stops short of explicitly naming a sibling, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is used before submission ('for user review before submission') and states that answers require actual applicant information and consent evidence, which is useful prerequisite context. It never says when to prefer it over amend_sms_application or get_sms_application, or what to do once a preview is accepted, so usage is only inferred.

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.

Resources