Skip to main content
Glama

find_german_b2b_leads

Search German B2B companies, crafts, and local businesses by keyword and location; filter results for verified phone numbers, websites, or contact details.

Instructions

Search German B2B companies, crafts (Handwerker), and local businesses via 11880 & Gelbe Seiten.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSingle search keyword alternative when 'search_terms' is omitted.
locationNoSingle city or postal code alternative when 'locations' is omitted.
locationsNoGerman cities, regions, or 5-digit postal codes, e.g. ['München', 'Leipzig'].
max_itemsNoMaximum number of B2B leads to extract (1-5000).
search_termsNoTrades, crafts, or industry keywords, e.g. ['Elektroinstallation', 'Solaranlagen'].
require_phoneNoOnly return businesses that have a verified phone number.
include_detailsNoFetch directory detail pages for corporate emails and full descriptions.
require_websiteNoOnly return businesses that have a corporate website/domain.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and does little with it. It never discloses that this scrapes live public directories (implying latency, possible rate limits or blocking), nor that include_details triggers extra detail-page fetches, nor that max_items up to 5000 can make a call long-running.

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?

A single front-loaded sentence with zero filler — verb, resource, and data sources in that order. Nothing in it is redundant with the title or schema.

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?

For an 8-parameter scraping tool with no annotations, the one-sentence description is insufficient: it omits operating behavior (latency, sourcing from public directories), the zero-required-parameter semantics, and how the filter flags interact. The output schema covers return values, but the invocation-context gaps remain.

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?

Schema description coverage is 100%, so every parameter is already documented with examples and defaults; the description adds no additional parameter meaning. Baseline 3 applies since the schema does all the work, including the query vs search_terms and location vs locations alternatives.

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

Purpose4/5

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

States a specific verb ('Search') plus concrete resources ('German B2B companies, crafts (Handwerker), and local businesses') and names the data sources (11880 & Gelbe Seiten). It is clearly distinct from siblings like check_german_company_kyb or search_german_public_tenders, though it never explicitly contrasts itself with them.

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 / when-not-to-use guidance, no mention of alternatives (e.g. using the KYB or Impressum tools for verification/enrichment instead), and no prerequisites. The only implicit signal is the named directory sources, which an agent must interpret on its own.

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