Liquid Agent

Local business leads: how many match (free)

leads_count

Read-onlyIdempotent

Free. How many local businesses match a category and place, how many have an email at each grade (A/B/C), the top cities, and the exact price of the next page. Run this before leads_search.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	5-digit ZIP (a prefix works).
`city`	No	City, e.g. Atlanta, Savannah, Macon. Give city, county, zip or near.
`near`	No	lat,lng to search around.
`email`	No	required (default), any, or none (phone-only businesses).
`limit`	No	How many leads, 1-1,000 (default 3 = $0.09); $0.03 per lead.
`county`	No	County, e.g. Gwinnett, Chatham.
`hiring`	No	Only businesses whose site says they are hiring.
`offset`	No	Skip this many, for the next page.
`sample`	No	true = 3 free leads to judge quality (3 a day), no payment.
`booking`	No	Online booking tool: yes, none, vagaro, square_appointments, calendly, booksy, mindbody, acuity, opentable, housecall_pro, jobber, servicetitan, zocdoc.
`website`	No	needs = no working website (a sales signal).
`category`	Yes	Business type in plain words: dentist, plumber, hvac, roofing, hair salon, law firm, med spa, restaurant.
`minGrade`	No	Email grade floor (A best). Default C.
`payments`	No	Payment system on their site: yes, none, square, toast, clover, stripe, paypal.
`radiusKm`	No	Radius for near, default 5.

Output Schema

TableJSON Schema

Name	Required	Description
`query`	No	The search as understood
`byGrade`	No	Count per email grade A, B, C, none
`matches`	No	Leads that match, with the email filter applied
`pricing`	No	How pricing works
`nextPage`	No	Leads and exact price of the next call
`topCities`	No	Cities with the most matches
`withEmail`	No	Matching businesses with a checked email
`businesses`	No	All matching businesses

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "businesses": {
+      "description": "All matching businesses",
+      "type": "number"
+    },
+    "byGrade": {
+      "additionalProperties": {},
+      "description": "Count per email grade A, B, C, none",
+      "properties": {},
+      "type": "object"
+    },
+    "matches": {
+      "description": "Leads that match, with the email filter applied",
+      "type": "number"
+    },
+    "nextPage": {
+      "additionalProperties": {},
+      "description": "Leads and exact price of the next call",
+      "properties": {},
+      "type": "object"
+    },
+    "pricing": {
+      "description": "How pricing works",
+      "type": "string"
+    },
+    "query": {
+      "additionalProperties": {},
+      "description": "The search as understood",
+      "properties": {},
+      "type": "object"
+    },
+    "topCities": {
+      "description": "Cities with the most matches",
+      "items": {},
+      "type": "array"
+    },
+    "withEmail": {
+      "description": "Matching businesses with a checked email",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / limit / description

Previous value: -"How many leads, 1-1,000 (default 10 = $0.30); $0.03 per lead."New value: +"How many leads, 1-1,000 (default 3 = $0.09); $0.03 per lead."

addedInput schema / properties / sample

Added value: +{
+  "description": "true = 3 free leads to judge quality (3 a day), no payment.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / limit / description

Previous value: -"How many leads, 1-1,000 (default 10 = $0.10); 100+ and 500+ per call cost less per lead."New value: +"How many leads, 1-1,000 (default 10 = $0.30); $0.03 per lead."

Changed3 schema fields changedOct 11, 2026

removedInput schema / properties / key

Removed value: -{
-  "description": "Your Liquid Leads plan key: plan leads are free, past the quota the overage pays per lead.",
-  "pattern": "^ll_[A-Za-z0-9]{32}$",
-  "type": "string"
-}

changedInput schema / properties / limit / description

Previous value: -"How many leads, 1-100 (default 25)."New value: +"How many leads, 1-1,000 (default 10 = $0.10); 100+ and 500+ per call cost less per lead."

changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +1000
```

AddedOct 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description earns credit for adding cost behavior: 'Free' plus disclosure that it surfaces 'the exact price of the next page'. Cost/pricing context is exactly the kind of behavioral detail annotations can't convey.

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?

Two tightly-packed sentences. 'Free.' is front-loaded as the key differentiator, followed by the counting scope and the sequencing directive. No wasted words.

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?

With an output schema present, the description needn't explain return values — yet it still summarizes them (grade counts, top cities, next-page price). Combined with 100% schema coverage on params, an agent has everything needed to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 15 parameters thoroughly (including pricing on limit and enum meanings). The description only loosely references 'category and place' and email grades, adding no syntax or format detail beyond the schema — baseline 3.

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 — counting how many local businesses match a category and place — and enumerates the return dimensions (counts by email grade, top cities, next-page price). This clearly distinguishes it from leads_search, which it positions as the follow-up step.

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 an explicit sequencing rule: 'Run this before leads_search', implying a free pre-flight check. It doesn't address the other siblings (leads_lookup, leads_tech) or state when not to use it, so guidance is clear but not exhaustive.

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

All Liquid Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Local business leads: how many match (free)

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources