Skip to main content
Glama

dieAnalysten Adressshop – German B2B company addresses

preis_berechnen

Read-only

Preis für eine Zielgruppe berechnen (netto/brutto, Rabatte, Mengenstaffel, Zahlart). Ändert nichts – es entsteht keine Bestellung.

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

Input Schema

NameRequiredDescriptionDefault
limitNonur so viele Firmen (Standard: alle passenden)
auswahlYesZielgruppe. Alle Angaben optional und UND-verknüpft (Regionen untereinander ODER). Werte für „merkmale“ liefert das Tool „kriterien“, Branchen das Tool „branchen_suchen“.
zahlartNo
optionenNoZusatzangaben wie im Shop (z. B. Telefon, E-Mail, Ansprechpartner)
gutscheinNoGutscheincode, falls vorhanden

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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; the description reinforces this with 'Ändert nichts – es entsteht keine Bestellung', which adds the concrete consequence (no order is created). Beyond that it says nothing about call cost, rate limits, or whether the computation runs over the live company set.

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 short, front-loaded clauses with no filler. The pricing dimensions come first and the safety statement second, matching the order an agent needs them.

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?

For a tool with five parameters, deeply nested filters and no output schema, the description never says what the result looks like (single price, per-unit breakdown, tier table) or whether the computed group size is reported. It is adequate to identify the tool but leaves a real gap about the return value.

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 coverage is 80%, so the nested 'auswahl' filters are already well documented in-schema. The description names the pricing levers (Rabatte, Mengenstaffel, Zahlart) that explain why a target group is needed, but it does not explain how selection size drives the Mengenstaffel or how 'optionen' affects the price. Baseline 3 is appropriate.

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 ('Preis für eine Zielgruppe berechnen') and lists the pricing dimensions covered (netto/brutto, Rabatte, Mengenstaffel, Zahlart). The closing clause 'es entsteht keine Bestellung' implicitly separates it from bestellung_anlegen, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

'Ändert nichts – es entsteht keine Bestellung' gives a clear usage context: this is a calculation/preview, not an ordering step. It does not explicitly route the agent to zielgruppe_zaehlen when only a count is wanted, so one alternative is left to inference.

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