Skip to main content
Glama

Search businesses

search_businesses
Read-onlyIdempotent

Search businesses in Costa Rica (or Panama with country: 'PA', Guatemala with 'GT', the Dominican Republic with 'DO') by industry, category, place, name and contact channel. Costs no credits: says which contacts each business has without revealing them, sorted by record quality. Combine industry and place with website, social, booking, min_rooms, email_type, ad_pixel, online_store, built_with and outdated_site to find the right target (spas that book on WhatsApp, businesses on Instagram with no website, stores that use Gmail, Wix sites not updated in years). Each result has signals with the same words: website, social, booking, booking_systems, rooms, email_type, ad_pixels, online_store, built_with, site_year (last update), no_mobile_version, no_https and opening_hours (OpenStreetMap format). Returns total and next_offset (null on the last page). Up to 3,000 results a day (100 until the account buys credits) and the first 1,000 of each search. detail: 'summary' drops signals and categories to save tokens.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the business name
limitNoResults per page (max 50, default 20)
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
detailNofull (default) or summary
offsetNoSkip this many results (use next_offset)
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: tienda (Retail and convenience stores), restaurante (Restaurants and cafés), hospedaje (Hotels and lodging), automotriz (Auto repair and parts), salon_belleza (Beauty salons and barbers), gimnasio (Gyms and fitness), spa (Spas), salud (Clinics, doctors and labs), veterinaria (Veterinary clinics), educacion (Private schools and academies), servicios (Professional services), construccion_hogar (Construction and home services), eventos (Events and parties), industria (Manufacturers and distributors), agro (Farms and agriculture), imprenta_medios (Printing, signs and media), transporte (Transport, freight and car rental), entretenimiento (Entertainment, sports and recreation), finanzas (Banks, lenders and credit unions), otros (Other businesses)
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.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: zero credit cost, 3,000 queries/day (100 until credits are purchased), first 1,000 results per search, quality-sorted output, and no contact data exposed. Those are exactly the operational constraints an agent needs before calling it.

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?

Purpose and scope are front-loaded, and every sentence carries operational information. The mid-section parenthetical filter lists make one sentence somewhat dense and run-on, but little could be cut without losing meaning.

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 20-parameter tool with no output schema, the description covers pagination ('total and next_offset, null on the last page'), result contents (signal names including site_year and opening_hours), throttling and the token-saving detail mode. Nothing essential to a correct call is missing.

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?

With 100% schema coverage the baseline is 3, and the description adds real value by mapping each filter concept to the corresponding result signal ('website, social, booking, booking_systems, rooms, email_type...') and by explaining that detail:'summary' drops signals and categories to save tokens.

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 and resource ('Search businesses in Costa Rica... by industry, category, place, name and contact channel') plus the country scope with enum codes. An agent can tell this is the primary filtered-discovery tool rather than a contact-reveal or list-management tool.

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?

Gives concrete usage patterns ('Combine industry and place with website, social, booking... to find the right target' with examples like 'spas that book on WhatsApp'). It also signals that contacts are described but not revealed, implicitly routing to a reveal tool, but it never names an exclusion or an explicit alternative.

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