Skip to main content
Glama

enrich_german_impressum

Extract § 5 DDG Impressum data from DACH domains, including CEOs, de-obfuscated emails, phone numbers, HRB and VAT IDs for B2B compliance and lead enrichment.

Instructions

Extract § 5 DDG / Impressum legal data, CEOs, de-obfuscated emails, phones, HRB & VAT IDs from DACH domains.

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

Input Schema

NameRequiredDescriptionDefault
urlNoSingle company domain or website URL to enrich.
domainsNoList of DACH company domains or URLs, e.g. ['biontech.de', 'celonis.com'].
max_concurrencyNoNumber of concurrent domain lookups (1-20).
extract_contact_pageNoAlso inspect /kontakt or /contact pages if email/phone is missing in Impressum.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add meaningful behavior beyond the name by disclosing that emails are de-obfuscated and that structured legal identifiers (HRB, VAT) are pulled, but it says nothing about fetching/crawling behavior, rate limits, failure modes, or what happens on non-DACH or unreachable domains.

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 dense sentence that front-loads the verb and the extracted data types, with zero padding. Every clause (legal data, contact details, registry IDs) earns its place.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the purpose is clear for a batch enrichment tool. However, for a network-crawling extractor the description omits behavioral essentials such as crawling scope, concurrency implications, and expected failure handling, leaving meaningful gaps.

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 the schema already explains url, domains, max_concurrency, and extract_contact_page. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Extract') plus a concrete resource set (Impressum legal data, CEOs, emails, phones, HRB/VAT IDs) and scope (DACH domains). This is clearly distinguishable from siblings like check_german_company_kyb or find_german_b2b_leads without opening a schema.

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

Usage Guidelines3/5

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

The DACH-domain scope implicitly tells an agent when the tool applies, and the domain-specific naming suggests it is a German legal-data extractor. But there is no explicit when-to-use vs. when-to-use-something-else guidance, no mention of prerequisites, and no hint about choosing between the 'url' and 'domains' inputs.

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