Skip to main content
Glama

Hail Communication for AI

Get verification requirements

get_verification_requirements
Read-onlyIdempotent

Read a carrier's current registration fields, documents, address rules and fees.

    The response's ``subject_types`` lists the applicant types the carrier accepts.
    US local SMS registration uses ``purpose="sms"``, country ``US`` and type ``local``.
    Toll-free verification uses ``purpose="sms"``, the number's country ``US`` or ``CA``,
    type ``toll_free`` and its owned ``number_id``. Each number needs its own verification.
    Applicant country and business tax status determine the registration route.
    The personal route is available to US or Canadian applicants without a business tax number.
    Local 10DLC fees apply at submission, carrier review and monthly after approval.
    Toll-free verification is free and sends no identity confirmation code.

    Returns ``required``, ``fields``, ``documents`` and ``address_required``.
    ``required=false`` means a registration submission is unnecessary and would fail.
    Fields and files require accurate information supplied by the authorized applicant.
    Choice fields accept comma-separated option keys within their ``min_choices`` and ``max_choices``.
    Field ``max_length`` uses UTF-16 code units; an emoji counts as two.
    Selected consent methods can require evidence even when shared fields are optional.
    Document slots with ``needs_input=false`` require no upload.
    An upstream failure returns an error.

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": {
      "country_code": "<country_code>",
      "number_type": "<number_type>",
      "subject_type": "<subject_type>"
    },
    "name": "get_verification_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoWhat the registration is for: ``number`` registers the applicant so a number can be bought; ``sms`` registers US texting (local 10DLC or toll-free).number
quote_idNoThe offer to register for: its ``quote_id`` from ``quote_numbers``, which selects that offer's form. Give it when ``purpose`` is ``number``; leave it out for ``sms``.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
number_idNoThe owned number this registration is for: its ID from ``list_numbers``, the same one used for the requirements. Give it for toll-free texting and when the form asks for the sending number; otherwise leave it out.
number_typeYesThe kind of number this registration covers. Copy it from the offer in ``quote_numbers`` or the number in ``list_numbers``.
country_codeYesISO 3166-1 alpha-2 country code, such as ``US``.
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
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
    • changedInput schema / properties / number_type / description
      Previous value: -"Kind of phone number: a local or mobile number, a national number (non-geographic), or a toll-free number."New value: +"The kind of number this registration covers. Copy it from the offer in ``quote_numbers`` or the number in ``list_numbers``."
  2. Changed8 schema fields changed
    • changedInput schema / properties / number_id / description
      Previous value: -"Owned number ID from ``list_numbers``, the same one used for the requirements. Required for toll-free texting verification and when the form asks for the sending number."New value: +"The owned number this registration is for: its ID from ``list_numbers``, the same one used for the requirements. Give it for toll-free texting and when the form asks for the sending number; otherwise leave it out."
    • changedInput schema / properties / number_type / description
      Previous value: -"``local``, ``mobile``, ``national`` or ``toll_free``."New value: +"Kind of phone number: a local or mobile number, a national number (non-geographic), or a toll-free number."
    • addedInput schema / properties / number_type / enum
      Added value: +[
      +  "local",
      +  "mobile",
      +  "toll_free",
      +  "national"
      +]
    • changedInput schema / properties / purpose / description
      Previous value: -"``number`` registers an applicant for a number purchase; ``sms`` registers US texting (local 10DLC or toll-free)."New value: +"What the registration is for: ``number`` registers the applicant so a number can be bought; ``sms`` registers US texting (local 10DLC or toll-free)."
    • addedInput schema / properties / purpose / enum
      Added value: +[
      +  "number",
      +  "sms"
      +]
    • changedInput schema / properties / quote_id / description
      Previous value: -"``quote_id`` of one offer from ``quote_numbers``. Required for ``purpose=\"number\"``; it selects that offer's form."New value: +"The offer to register for: its ``quote_id`` from ``quote_numbers``, which selects that offer's form. Give it when ``purpose`` is ``number``; leave it out for ``sms``."
    • 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/openWorld, so the bar is lowered, yet the description still adds substantial operational context: fee timing (at submission, carrier review, monthly after approval), toll-free being free with no identity confirmation code, required=false semantics, document slots with needs_input=false needing no upload, and upstream failures returning an error. It stops short of permission/auth requirements or any read-scope caveats, keeping it below a 5.

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

Conciseness3/5

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

The description is front-loaded well and each paragraph addresses a distinct concern (purpose, scenarios, fees, return contract, field formatting), but it runs long and includes material that duplicates structured data — notably the 'Returns required, fields, documents and address_required' line despite an existing output schema, and the generic line about accurate information from the authorized applicant.

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 7-parameter, enum-heavy read tool with an output schema, the definition covers the gaps an agent would otherwise hit: UTF-16 code-unit length counting with emoji as two, comma-separated choice keys bounded by min_choices/max_choices, consent evidence even when shared fields are optional, and needs_input=false slots. The absence of explicit workflow positioning relative to sibling verification tools is the main remaining hole.

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%, so the baseline is 3, but the description earns more by explaining cross-parameter combinations the schema documents only in isolation: purpose="sms" pairs with country/type combos, number_id is required for toll-free, and applicant country plus business tax status determines whether the personal route is available. This is genuine meaning beyond the per-field descriptions.

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 gives a specific verb and resource set: reading a carrier's registration fields, documents, address rules and fees. It is unambiguous what the tool returns, but it never names a sibling (e.g., get_verification or submit_verification) to draw the boundary between reading requirements and reading/submitting an existing registration.

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?

Usage is implied through scenario routing — US local SMS uses purpose="sms"/US/local, toll-free uses purpose="sms"/US or CA/toll_free with number_id — and through the note that required=false means a submission would fail, which hints this is a pre-check. However, it never explicitly says when to call this versus the other verification tools (submit_verification, check_verification, get_verification), so an agent must infer the workflow position.

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