Skip to main content
Glama

Data Candy: US business leads

Preview leads

preview_leads
Read-onlyIdempotent

Show up to 10 sample leads for the filters with email, phone and last name partly hidden, plus the total number of matches. Free; use it to check the filters return the kind of businesses you want.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sample rows (1 to 10, default 5).
filtersNoSearch filters, all optional. Combine as needed; more filters means fewer leads.

Output Schema

NameRequiredDescriptionDefault
rowsYesMasked sample rows (email, phone and last name are partly hidden).
countYesTotal leads matching the filters.
shownYes
filtersYes
ignored_filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: a hard 10-row cap, deliberate PII masking on email/phone/last name, inclusion of the total match count, and the fact that the call costs nothing. That is real value beyond the structured fields.

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?

A single compact sentence pair with the most decision-relevant facts (row cap, masking, total count, free) front-loaded and no filler. Slightly awkward phrasing ('check the filters return') keeps it from being perfect.

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?

With an output schema present and fully documented nested filter params, the description needn't explain return values, and it still usefully flags the cap and masking. Nothing an agent needs to invoke it correctly is missing.

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%, including nested filter properties with constraints, examples, and a pointer to list_industries for category/industry names. The description only alludes to 'the filters' generically and adds no syntax or semantics beyond the schema, so the 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?

The description gives a specific verb ('Show') plus resource ('up to 10 sample leads') and even characterizes the payload: masked email/phone/last name plus a total-match count. That makes it distinguishable from count_leads or buy_leads in practice, though no sibling is named explicitly.

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?

'Free; use it to check the filters return the kind of businesses you want' gives a clear condition for selecting this tool over a paid purchase path. It stops short of naming an alternative or stating when not to use it, so it lands just below the top band.

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