Skip to main content
Glama
hail-hq

hail

Official

Quote phone numbers

quote_numbers
Read-onlyIdempotent

Compare live phone-number offers from carriers by country, capabilities, number type, and location to find a ready-to-buy number.

Instructions

Compare live phone-number offers from the carriers. Read-only: it buys nothing and charges nothing.

    ``country_code`` is an ISO alpha-2 code such as ``"US"``.
    ``capabilities`` is ``["voice"]``, ``["sms"]`` or both (default).
    ``number_type`` is ``local``, ``mobile``, ``national`` or
    ``toll_free``; omit it to compare all types.
    ``area_code`` is an area code or the first digits of the number, as
    dialed in the country: ``"020"`` (London), ``"480"`` (Arizona).
    ``city`` is a city name such as ``"London"``. Each offer has
    ``locality`` and ``region`` (such as ``"Phoenix"``, ``"AZ"``): check
    them, since city names repeat across states. ``region`` (optional,
    with ``city``) is a US/CA state code; list_number_regions lists them.
    Omit all three to search the whole country.

    Returns ``{"offers": [...], "recommended_quote_id", "expires_at"}``.
    Each offer has ``e164``, ``number_type``,
    ``capabilities``, ``monthly_cents``, ``setup_cents``, ``readiness``,
    ``requirements``, ``subject_types``, ``verifications`` and
    ``quote_id``. Money fields are cents (USD).
    Quotes expire in 10 minutes (``expires_at``); quote again after that.

    ``subject_types`` says who may verify for the number: ``person``
    (the user), ``business`` (the user's company), or both; empty when no
    verification is needed. ``verifications`` lists the verifications
    the offer can be bought with (``id``, ``state``, ``subject_type``,
    ``subject_name``), approved first: those of an accepted subject type
    still under review, and the approved ones the carrier still accepts
    for the offer. ``subject_name`` is the person's or company's name from the
    verification form. When several are approved, show the user the
    names and ask which one buys the number; pass its ``id`` as
    ``verification_id`` to acquire_number.

    An offer with ``readiness == "verification_required"`` cannot be
    bought until the organization is verified. Ask the user "you or your
    company?" to pick the ``subject_type`` (one of ``subject_types``).
    Call get_verification_requirements, ask the user for the details,
    then submit_verification, both with the offer's ``quote_id`` and that
    ``subject_type``, and poll get_verification (review takes business
    days). ``requirements``
    lists what the carrier needs. Prefer an offer whose
    ``readiness`` is ``"ready"``; ``recommended_quote_id`` points at the
    best one, or is null if none is ready.

    An offer with ``by_request: true`` has no ``e164``: support orders
    that number by hand. acquire_number refuses it; tell the user to ask
    support. Its ``quote_id`` still works for verification.

    Errors come back as ``{"error": "<message>"}``.

Input Schema

NameRequiredDescriptionDefault
cityNo
regionNo
area_codeNo
number_typeNo
capabilitiesNo
country_codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.30.0
    • removedInput schema / properties / provider
      Removed value: -{
      -  "default": "auto",
      -  "title": "Provider",
      -  "type": "string"
      -}
  2. First observedv0.29.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: quotes expire in 10 minutes, money is in cents, by_request offers cannot be acquired directly, verification-required offers need a workflow, and errors are returned as an error object. These details are critical for correct invocation and do not contradict the read-only annotations.

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 description is long but appropriately structured and front-loaded with the core purpose and read-only guarantee. Some return-field detail is redundant with the output schema, but the information is organized and largely earns its place given the tool's complexity.

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?

The description is complete for a complex quoting tool: it covers all parameters, return semantics, expiration, verification workflows, error format, and edge cases like by_request offers. Together with the existing output schema and annotations, an agent has everything needed to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining every parameter: country_code format, capabilities options and default, number_type values, area_code examples, city usage, and region semantics. It also explains interactions such as omitting all location filters to search the whole country.

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?

The description states a specific verb and resource: compare live phone-number offers from carriers. It also clarifies the read-only nature and distinguishes quoting from buying, so an agent can identify the tool's role without opening the 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?

The description gives clear usage context, including how to handle verification-required offers, by-request offers, quote expiration, and passing verification_id to acquire_number. It does not explicitly state when not to use this tool versus siblings like list_numbers, so it falls short of a full when/when-not/alternatives guide.

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