Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

b2b_company_decision_maker_email_finder

Read-onlyIdempotent

B2B Company & Contact Enricher (Verified Emails): Real-time structured data extraction feed for B2B Company & Contact Enricher (Verified Emails).

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_company_decision_maker_email_finder"
  }
}

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 and idempotency profile is covered. The only added claim is 'Real-time', which says nothing about what data is returned, how the external lookup behaves on failure, or any rate/quota constraints an open-world feed would typically have.

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 every word is wasted: the title is repeated verbatim twice with no front-loaded statement of purpose. Brevity here reflects under-specification rather than conciseness.

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?

With no output schema, the description should explain what records come back (companies, contacts, verified emails, fields) and what verification means. None of that is present, leaving an agent unable to predict results from an enrichment/feed tool.

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?

Only one optional parameter (maxResults) exists and its schema description is fully covered, so the schema carries the burden adequately. The description adds no meaning about what maxResults counts or how results are ranked or paged, which is the baseline-3 outcome for high schema coverage.

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 description merely restates the title twice: 'B2B Company & Contact Enricher (Verified Emails): Real-time structured data extraction feed for B2B Company & Contact Enricher (Verified Emails).' It never mentions decision makers or email finding, which is what the tool name claims, and offers no specific verb+resource pairing that distinguishes it from siblings like linkedin_b2b_executive_finder_verified_email or b2b_leads_finder_verified_emails.

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 guidance, no prerequisites, and no mention of alternatives among the many similarly named B2B sibling tools. The agent is left to infer selection purely from the tool name.

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