Skip to main content
Glama

dieAnalysten Adressshop – German B2B company addresses

zielgruppe_zaehlen

Read-only

Wie viele Firmen in Deutschland passen zur gewünschten Zielgruppe? Liefert die Anzahl kaufbarer Adressen und die Datenabdeckung (Telefon, E-Mail, Website, Ansprechpartner).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "auswahl": "<auswahl>"
    },
    "name": "zielgruppe_zaehlen"
  }
}

Input Schema

NameRequiredDescriptionDefault
auswahlYesZielgruppe. Alle Angaben optional und UND-verknüpft (Regionen untereinander ODER). Werte für „merkmale“ liefert das Tool „kriterien“, Branchen das Tool „branchen_suchen“.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the return composition (number of buyable addresses plus coverage of phone, e-mail, website, contact person), which matters since no output schema exists. It says nothing about cost/credit consumption, result freshness, or whether counts are estimates — relevant for a commercial address database.

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?

Two sentences: the first frames the question the tool answers, the second enumerates the returned data. No filler, and the core purpose is front-loaded.

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

Completeness4/5

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

Given a single deeply nested object parameter with full schema documentation and no output schema, the description carries the return-value burden and does so concisely. What is missing is a note on whether counting is free/side-effect-free and how the count relates to placing an order, which a lead-generation agent would want.

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% and the nested 'auswahl' object documents each filter, its value sources, and the AND/OR combination logic. The description itself adds no parameter 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.

Purpose4/5

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

The description names a specific verb and resource ('Wie viele Firmen … passen zur gewünschten Zielgruppe?') and states the two outputs: count of purchasable addresses plus data coverage. It is clearly a counting/qualification tool, distinguishable from a lookup like branchen_suchen, though it never names a sibling to route against.

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?

Usage is only implied: the question form suggests an audience-sizing / pre-check step before ordering, but the description never says when to use this versus preis_berechnen or bestellung_anlegen, nor does it state prerequisites. The schema does point to 'kriterien' and 'branchen_suchen' for value discovery, but that guidance lives in the schema, not the description.

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