Skip to main content
Glama

Data Candy: US business leads

Count leads

count_leads
Read-onlyIdempotent

Count the leads that match the filters (industry, category, keyword, state, city, ZIP, has_email, has_cell and so on). Fast and free; nothing is charged. Returns the count and whether it is exact.

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": "count_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoSearch filters, all optional. Combine as needed; more filters means fewer leads.

Output Schema

NameRequiredDescriptionDefault
countYes
exactYes
filtersYes
capped_atNo
ignored_filtersNoFilters the catalog could not apply, if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context — the call is fast and incurs no charge — which is decision-relevant information not captured in 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?

Two short sentences with the cost cue front-loaded after the purpose; nothing is padded. The trailing "and so on" is slightly loose given the schema is exhaustive, but overall it is tight and well-ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure needn't be explained, yet the description usefully notes the count plus an exactness flag. However, it never explains when a count might be inexact, leaving the agent unsure how to interpret that flag.

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% and the nested filters object documents every field including examples and combination semantics, so the schema carries the burden. The description only restates a subset of filter names (industry, category, has_email, has_cell) without adding format or constraint detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Count the leads that match the filters") and enumerates the filter dimensions it accepts, so the tool is immediately identifiable. It does not explicitly name or contrast with siblings such as preview_leads or quote_leads, though "Fast and free; nothing is charged" implicitly separates it from the purchasing tools.

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

Usage Guidelines3/5

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

Usage is implied: call this to get a cheap/free count of a filtered lead set. The "nothing is charged" clause hints at preferring this over quote_leads/buy_leads when only a number is needed, but no explicit when-to-use/when-not or named alternative is given.

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