Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

b2b_leads_finder_verified_emails

Read-onlyIdempotent

B2B Leads Finder with Built-in MX Email Verification: Real-time structured data extraction feed for B2B Leads Finder with Built-in MX Email Verification.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — 'real-time' and 'structured data extraction feed' are unelaborated marketing phrasing that never clarify what a lead record contains, how MX verification results are surfaced, or whether external network lookups incur cost or latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the second clause is a near-verbatim repetition of the first with filler qualifiers ('Real-time structured data extraction feed'). No useful information is front-loaded because none is present.

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

Completeness2/5

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

Although the tool is simple (one optional parameter, annotations supplied, no output schema), the description leaves the core unknown: what a lead record looks like, what 'verified' means in the response, and whether results are fresh or cached. For a discovery tool with no output schema, this is a meaningful gap.

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?

There is a single optional parameter (maxResults) whose schema description is present and complete at 100% coverage, so the schema carries the semantics. The description does not add anything about result limits or pagination, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text says it is a 'B2B Leads Finder with Built-in MX Email Verification' and then repeats that same phrase as a 'real-time structured data extraction feed.' This is essentially a restatement of the tool name and annotation title rather than an explanation of the operation, and it never distinguishes the tool from siblings such as linkedin_b2b_executive_finder_verified_email or b2b_company_decision_maker_email_finder.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of any alternative tool. The domain hint ('B2B leads') weakly implies leads-prospecting use, but an agent gets no signal about selecting this over the many adjacent finder/enricher siblings.

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