Skip to main content
Glama

Data Candy: US business leads

Quote a purchase

quote_leads
Read-onlyIdempotent

Exact price for buying quantity leads for the filters. Nothing is charged. Returns how many leads match, the price in dollars and the payment methods available right now.

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": {
      "quantity": "<quantity>"
    },
    "name": "quote_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoSearch filters, all optional. Combine as needed; more filters means fewer leads.
after_idNoContinue after this lead id (use next_after_id from an earlier order to get new leads).
quantityYesHow many leads (1 to 25,000). If fewer match, you get what matches.

Output Schema

NameRequiredDescriptionDefault
filtersYes
matchedYesLeads matching the filters.
quantityYesHow many leads the price is for.
price_usdYes
price_centsYes
expires_in_sNo
ignored_filtersNo
payment_methodsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, idempotent operation. The description adds important behavioral context beyond those annotations: it does not charge anything and returns matching lead count, dollar price, and currently available payment methods.

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?

The description is three short sentences that front-load the core purpose and then clarify cost and return behavior. Every sentence adds useful information without repetition or filler.

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?

Given that the input schema is fully documented, annotations cover safety semantics, and an output schema exists, the description supplies enough context to call the tool correctly. It could be slightly stronger by explicitly relating the quote step to a subsequent purchase action, but nothing critical 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%, so the schema already explains quantity, filters, and after_id in detail. The description reinforces that quantity and filters drive the quote, but it does not add meaning beyond the schema, such as how after_id affects the quote.

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?

The description states a specific verb and outcome: exact price for buying a specified quantity of leads for filters, and explicitly says nothing is charged. This distinguishes it from a purchase action such as buy_leads by emphasizing that it is a quote, not a transaction.

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?

The description implies use before purchasing by saying it returns an exact price and 'Nothing is charged,' which signals a quoting context. However, it does not explicitly name buy_leads, count_leads, or preview_leads as alternatives, nor does it state when not to use this tool.

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