LeadMarina

Enrich business domains

enrich_domains

Already have businesses? Pass up to 10 website domains to run the full enrichment + verification pipeline on them (verified emails + phones, owner name, socials). Costs 1 lead per distinct domain — spellings of the same site (acme.com, www.acme.com, https://acme.com/contact) count once. Returns a search_id to poll with get_search_results. US businesses only for now: their phones are read as US numbers.

Input Schema

Name	Required	Description	Default
`domains`	Yes	Business domains, e.g. ['acme.com'] (max 10).

Output Schema

Name	Required	Description
`note`	No	Present when a delivered domain was listed more than once, or when the balance left some domains out (named, not charged).
`enriching`	Yes	Domains accepted (balance-capped).
`next_step`	No
`search_id`	Yes
`enrichment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Present when a delivered domain was listed more than once, or when the balance left some domains out (named, not charged).",
+  "type": "string"
+}

First observedJul 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), and the description adds substantial non-obvious behavior: 1 lead charged per distinct domain, spelling-variant deduplication, US-only phone handling, and the returned search_id polling flow.

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?

Three tight sentences, front-loaded with the precondition, then cost rules, then the return/polling contract. Every clause carries information; nothing is filler.

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

Completeness5/5

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

Despite an output schema, the description still supplies the essential async contract (search_id → get_search_results), covers cost and eligibility limits, and fully specifies the one input. An agent has everything needed to call and follow up correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single documented array parameter, so the baseline is 3. The description adds real meaning beyond the schema by explaining the max-10 limit in context and, crucially, the distinct-domain billing/dedup semantics that the schema does not convey.

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?

States a specific verb+resource (run enrichment + verification pipeline on website domains) and lists exactly what is produced (verified emails/phones, owner name, socials). It is clearly distinguishable from siblings like search_leads and get_search_results.

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?

The opening 'Already have businesses?' frames the precondition for using this tool instead of a search tool, and it explicitly routes the follow-up to get_search_results by name. There is no explicit when-not-to-use or named alternative for the 'I don't have domains' case, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LeadMarina tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.