get_quotePrice one or more phone-lead lists exactly as the Leads Fresh DB shop charges them (live prices, volume discounts included) and get the link to order. Nothing is ordered.
| Name | Required | Description | Default |
|---|---|---|---|
| lists | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / lists / items / properties / age_maxRemoved value: -{
- "description": "For mixed only.",
- "maximum": 100,
- "minimum": 18,
- "type": "integer"
-}Input schema / properties / lists / items / properties / age_minRemoved value: -{
- "description": "For mixed only.",
- "maximum": 100,
- "minimum": 18,
- "type": "integer"
-}Input schema / properties / lists / items / properties / filter / descriptionPrevious value: -"Which list: old = Old people 55+ — men, women or both, aged 55 to 100 (option: gender); mixed = Any age & gender — the age range and gender the campaign needs (options: gender, age_min, age_max); business = Business numbers only — shops, clinics, garages, cafés; ios = iPhone users only; rcs = RCS-ready numbers (rich cards, images, buttons); photo = Chosen by what the profile photo shows, e.g. dog lovers, garden lovers (option: interest); carrier = Only numbers on one mobile network (option: carrier); any other filter can be limited to a network too"New value: +"Which list: old = Old people 55+ — men, women or both, aged 55 to 100 (option: gender); mixed = Mixed age & gender — every age 0–100 mixed, men, women or both (option: gender); business = Business numbers only — shops, clinics, garages, cafés; ios = iPhone users only; rcs = RCS-ready numbers (rich cards, images, buttons); photo = Chosen by what the profile photo shows, e.g. dog lovers, garden lovers (option: interest); carrier = Only numbers on one mobile network (option: carrier); any other filter can be limited to a network too"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotent/destructiveHint=false; the description adds meaningful context that pricing is live, includes volume discounts, and returns an order link while nothing is actually ordered. That reinforces and enriches the safety profile rather than merely repeating it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences with the core action and the no-side-effect guarantee front-loaded. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only quote tool with no output schema, the description covers the essential behavior and hints at the return value (order link). It could say more about how pricing errors or unsupported countries are surfaced, but nothing critical for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The top-level "lists" parameter has no description in the schema, and the description only clarifies that it accepts one or more lists. It says nothing about the 20-list cap, the 1000–50000 quantity steps, or the filter/gender/carrier options, though the nested schema properties document those well.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (price) and resource (phone-lead lists), plus scope (live prices, volume discounts) and result (link to order). It doesn't explicitly name the sibling tools, but "Nothing is ordered" makes the quote-vs-order intent unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the workflow (get a quote and an order link) but never says when to use this instead of get_catalog or get_free_sample, nor what prerequisites exist before pricing a list. Usage is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.