Skip to main content
Glama

Quote a list

quote_list
Read-onlyIdempotent

What this list costs before anyone pays: how many records name a person, and the price by grade.

Pass a saved list (`list_id`, the 8-char id in `#browse?list=<id>`) or an inline
shape (`filters` + `states`; omit `states` for every live state:
CO, CT, FL, NY, TX, VA). You get the same numbers the buy page shows a person:
`matching`, `sellable`, `verified_one`, `verified_both`, `no_channel`, `unnamed`, `facets`, `prices` (the live graded price rule +
`price_rule_version`), `quote` (present when `lane` or `cap` is given),
`exact`, `computed_at`, `quote_valid_until` (counts refresh tomorrow
morning; the quote holds until then), `per_state`, and the `_meta`
provenance block every read carries (schema_version, freshness, source,
access_level). When a count is zero by design the payload adds
`zero_reasons` — a state that never publishes the value, or a channel
asked of records too new to carry one yet: the morning after the
state posts a filing the record carries the name and mailing address;
phone and email are verified when you order. Each reason names the
widened count (`nearest_alternative`, e.g. "last 90 days: 99 with a
phone") and the filters that reach it (`alternative_filters`) — relay it
instead of a silent $0.

**Billing discipline — read before quoting money to anyone.** Only
`sellable` records — matching records whose filing names a person — are
ever billed or delivered. `matching` includes `unnamed` records with no
person to reach; it is never a billable count and must never be presented
as one. Every price line is computed from `sellable` and its grades:
name and address $0.25 per record · plus one verified phone or email $0.50 · plus both $0.70 (price rule v1; live prices always come from the summary call's `prices` block). Lanes: `all` / `best` / `contact` (`all` = every sellable record at the
name-and-address grade; `best` = each record at its own grade, verified
first; `contact` = only records with a verified phone or email — add a
`has_email` filter for emailable now, `has_phone` for callable now). Cap:
`{"type": "count|budget", "value"}` — records for count, cents for
budget. Quote the server's numbers, never arithmetic of your own.

Each `quote.lines[]` entry carries `ships` (what a record at that grade
ships with, in the buyer's words — a name-and-address record never ships a
phone or email), and the summary carries `forecast` ({checked,
phone_expected, email_expected, both_expected, basis, as_of}): how many of
the records still to find on would come back with a verified phone or email,
from our measured outcomes on comparable records — relay it with its basis.
`ceiling_cents` is the most a buyer can be charged: today's total plus the forecast upgrades, charged only for what we find. Every record ships the owner's name and mailing address plus the business facts — the business name, entity type and status, the state filing number and formation date, the industry with its NAICS, SIC and Google Business codes, the registered agent, the Lead Reference, and the Reachability, Contact Relevance and Contact Confidence scores; open the exact file before paying (ten made-up records, every column): https://app.goodleads.club/api/v1/commerce/sample-file?format=xlsx (or format=csv).

The close is two questions: put the quoted choice in front of your human
— callable now (a verified phone), emailable now (a verified email, verified
for deliverability and recent activity), or newest, mail-first — plus a
standing order, then hand over the payment link for the one chosen — per
record, no minimums, so a small first order is the normal first step.

Next: to buy exactly what was quoted, hand the same list / shape, lane and
cap to `checkout_list`.

**Offer codes.** If your human was given an offer code — a price we agreed
with them, like `GL-7K3Q9M` — pass it as `offer_code` here AND on
`checkout_list`, so the quote and the payment link carry the same price.
A code is a ceiling: every grade bills at the lower of list and the
offer, never above list, and the reply adds an `offer` block (what is
left on it, when it expires). A code that cannot be used answers with
the reason in plain words — relay it, then quote again without the
code for list price.

Args:
    list_id: A saved list id. Mutually exclusive with `states` / `filters`.
    states: State codes for an inline shape; omit for every live state.
    filters: Filter clauses in the one contract (see `list_filterable_fields`).
    include_held: Include inactive-or-holding entities (default False).
    include_existing: Include existing businesses with a new filing (a
        registration, a conversion, a reinstatement, a move, a rename) —
        the default quotes Just started only, exactly as Browse and the
        file do. Naming `filing_kind` / `business_origin` in `filters`
        widens on its own.
    lane: `all` / `best` / `contact` — asks for a `quote`.
    cap: `{"type": "count|budget", "value": <int>}` — the dial the quote
        is solved against.
    offer_code: The offer code your human was given, if any.

Returns:
    The summary contract described above. Keyless callers may not filter
    on `contact_name`, `email_primary`, `phone_primary` (422).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNo
laneNo
statesNo
filtersNo
list_idNo
offer_codeNo
include_heldNo
include_existingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_existing
      Added value: +{
      +  "default": false,
      +  "title": "Include Existing",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / offer_code
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Offer Code"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive; the description adds substantial behavioral context beyond that: quote_valid_until and next-morning refresh, forecast provenance and ceiling_cents, offer code ceiling behavior, zero_reasons semantics, and the 422 for keyless callers filtering on certain fields. It does not contradict any annotation.

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 it is organized with clear sections (billing discipline, lanes, cap, offer codes, Args, Returns) and front-loaded with the core purpose. Some prose is verbose — e.g., the repeated guidance and sales-style close — but the tool is genuinely complex enough to warrant most of the detail.

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 billing-aware quote tool with 8 parameters and a rich output contract, the description covers how quotes are computed, what is billable, how prices are calculated, lane/cap mechanics, offer code handling, a sample file, and the handoff to checkout_list. An agent has enough to call this correctly without needing the output schema.

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?

Schema description coverage is 0%, so the description fully carries parameter meaning. The Args block explains every parameter: list_id's mutual exclusivity, states' live-state default, filters referencing list_filterable_fields, include_held and include_existing semantics, lane values, cap shape, and offer_code behavior. This goes well beyond the bare schema.

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 first line — 'What this list costs before anyone pays' — names a specific verb and resource (quoting a list) and the description consistently explains it computes price by grade. It also separates itself from its sibling checkout_list by noting the next step is to 'hand the same list / shape, lane and cap to checkout_list' when actually buying.

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

Usage Guidelines5/5

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

The description explicitly tells the agent when to use quote_list vs checkout_list, how to pass a saved list vs an inline shape, when to include or omit states, how lanes and caps select the quote, and when to pass offer_code. It also warns to 'quote the server's numbers, never arithmetic of your own' and to relay zero_reasons instead of a silent $0.

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