Skip to main content
Glama

Quote a contact list

quote_list
Read-onlyIdempotent

Prices a list before buying it. Takes the same filters as search_businesses plus how many businesses you want (up to 200) and says how many match, how many of the first count with contacts you already revealed (free again) and how many credits the rest would cost, with a 10-row sample. Spends no credits. Show the person the price, then call build_list with the same filters.

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": {
      "count": "<count>"
    },
    "name": "quote_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the business name
countYesHow many businesses the list should have (max 200)
placeNoProvince, canton or district in Costa Rica (e.g. 'Escazú', 'La Fortuna', 'Heredia'); in Panama, province, district or corregimiento (e.g. 'Chiriquí', 'David', 'Bella Vista'); in Guatemala, department or municipality (e.g. 'Quetzaltenango', 'Mixco'); in the Dominican Republic, province or municipality (e.g. 'La Vega', 'Santo Domingo Este'). Accents optional
socialNoOnly businesses with this social profile
bookingNoHow they take bookings: through WhatsApp, without a booking system (phone, email, form) or with one. Known for about 1,500 businesses, mostly spas, salons and hotels
channelNoOnly businesses with this contact (mobile: a mobile number published as a phone, likely WhatsApp)
countryNoCR (Costa Rica, the default), PA (Panama), GT (Guatemala) or DO (Dominican Republic)
websiteNonone: no website (or it is down or parked); has: a working website
ad_pixelNotrue: its own website has a Meta or TikTok ad pixel
categoryNoCategory slug inside the industry, e.g. barberia, odontologia, pulperia_minisuper, taller_mecanico, hotel. list_categories has them all; an unknown one comes back with the valid ones
industryNoIndustry slug, named in search_businesses and list_categories
min_roomsNoHotels: at least this many rooms
built_withNoOnly businesses whose own website is built with this CMS or site builder
email_typeNoown_domain: email on the business's own domain; free: Gmail, Hotmail, Outlook, Yahoo, iCloud and similar
online_storeNotrue: its own website is an online store (Shopify, WooCommerce with products, PrestaShop…)
outdated_siteNotrue: its own website shows no update in two years or more (copyright year or page dates)
independent_onlyNotrue: small businesses only, no chain locations
min_whatsapp_confidenceNoMinimum WhatsApp confidence, 0 to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantive traits beyond them: it spends no credits, already-revealed contacts are counted free, and it returns match count, recoverable count, credit cost and a 10-row sample. That is exactly the economic and side-effect information an agent needs before a purchase step.

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?

Three sentences, front-loaded with the core purpose, then the return shape, then the required next action. The long middle sentence is dense but every clause (match count, free re-reveals, credit cost, sample) carries distinct information.

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 an 18-parameter tool with no output schema, the description compensates by describing the return payload in prose and by anchoring the filter set to search_businesses. No behavioral or procedural gap remains that would cause a mis-call.

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 parameter meanings are already documented; the baseline would be 3. The description adds framing beyond the schema by saying the filters are the same set as search_businesses and that `count` is capped at 200, tying 18 parameters to a familiar mental model.

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 specific verb ('Prices a list before buying it') and the exact resource, and immediately differentiates itself from build_list as the preview-only step. An agent can tell what this does and what it does not do 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?

Explicit workflow guidance: show the price to the person, then call build_list with the same filters, and it names search_businesses as the filter source. It stops short of an explicit 'use search_businesses instead when you want to browse raw results', so it is clear context rather than full when/when-not routing.

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