pricing_infoFree — list every paid tool in the 'lead-intelligence' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Free' and the instruction to call it first, which conveys no-cost access and an ordering dependency—useful context beyond the annotations.
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?
The entire description is one efficient sentence, front-loaded with 'Free' and a clear action. Every phrase adds value with no redundancy.
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 zero-parameter, read-only tool with no output schema, the description covers what it does, what it returns, its cost, and when to use it. It is fully adequate for the agent to select and invoke correctly.
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 tool has 0 parameters, so the description need not explain parameter behavior. The baseline of 4 applies, and the description reinforces that no input is required.
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?
The description clearly states the tool lists every paid tool in the 'lead-intelligence' bundle with price, payTo address, and network. It uses a specific verb ('list') and resource, and it distinguishes itself from sibling lead-finder tools by focusing on pricing.
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 explicitly says 'Call this first if you don't have a wallet ready yet,' providing a clear condition for when to invoke it. It does not mention when not to use it or name alternatives, but this context is sufficient for the tool's simple role.
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.
Each tool targets a distinct lead-intelligence function: scraping careers pages, finding booking gaps, verifying published emails, identifying hiring managers, cleaning lists, and detecting permits. The two vertical gap finders (clinic and restaurant) are structurally similar but clearly separated by domain in both names and descriptions, avoiding real confusion.
Most names follow a lowercase hyphenated descriptive pattern (e.g., 'careers-page-scraper', 'lead-list-cleaner'), but 'pricing_info' breaks the pattern by using an underscore. The naming is readable and mostly consistent, yet it lacks a uniform verb_noun convention across the set.
With 8 tools, the server is well-scoped for a lead-intelligence bundle, covering the lead lifecycle from discovery to enrichment to cleaning. This falls comfortably within the ideal 3-15 range, and no tool feels redundant or out of place.
The set covers lead discovery (careers, permits, gap finders), enrichment (domain-to-email, hiring-manager-email), and processing (lead-list-cleaner), forming a coherent workflow. Minor gaps exist—like a general web-search lead finder or a tool to update lead statuses—but they don't break the core pipeline.